CICERO — the house voice. The numbered communication rules under one governing readability rule (result first, plain words, recommend one option, push back with reasons, honesty about verification, stay in scope) ship as a force-for-plugin output style applied at the system-prompt level. Four floor rules are invariants; every other rule is a user-overridable default. 2.3.0 inverts the shape default: prose unless a trigger fires, with a checkable situation-to-shape map, a ban on two adjacent blocks sharing a shape, a measured device inventory in which bold is no longer load-bearing, and a bar-and-title heading. The honesty floor now forbids ending a turn on a promise — a turn ends DONE, BLOCKED, or CONTINUING-and-continuing — because asking an agent to narrate its progress is itself a documented cause of premature stopping. 2.5.0 adds an unambiguity section borrowed from ASD-STE100: one term for one thing inside a document, a noun cluster of at most three words, the condition stated before the instruction, and a ban on dropping a word to hit a length target. That standard's approved-word dictionary and its ban on -ing forms are deliberately not adopted. A SessionStart hook shows a banner with a worked example of the finding-tree notation and picks the conversation language; a UserPromptSubmit hook keeps the reply language current.
2 on GitHubby Roman Maslennikovv2.5.2updated 3 days ago
/
Plugin cicero from marketplace bladeforge in aquivalabs/BladeForge. Commands read from the repo's manifest — 2 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
Stack-agnostic pre-push review framework — eight reviewer agents (five on by default, plus skill, leak and security-scan for repos that publish skills), the /review orchestrator, and the secret-scan + attestation gate, all driven by a per-project .claude/review.config.json.
Whose Turn, the Claude Code side of a local monitor of your Jira, GitHub, Linear and other sources: whose turn it is, what changed, your own to-dos, a summary at the start of each session, a hand-off from the monitor window into the session, a /whose-turn command that opens the window, and an MCP server for any agent. The monitor itself is the published whose-turn npm package; the plugin installs its latest version into the monitor's data directory on first start and runs it from there; each newer version is then announced in its window and at session start and installs only when the user says yes or clicks Update. Employer-specific values live in a workspace config on the machine, not in the plugin.
Collection of example skills demonstrating various capabilities including skill creation, MCP building, visual design, algorithmic art, internal communications, web testing, artifact building, Slack GIFs, and theme styling
Comprehensive toolkit for developing Claude Code plugins. Includes 7 expert skills covering hooks, MCP integration, commands, agents, and best practices. AI-assisted plugin creation and validation.
Agentic QE (external: maintained in proffesor-for-testing/agentic-qe, pinned to v3.15.17): a quality-engineering fleet with 11 QE agents, 9 skills, 9 commands, the agentic-qe MCP server pinned to the plugin version, and the aqe-mod guard that refuses destructive operations on AQE learning data
Headroom startup hooks for Claude Code and GitHub Copilot CLI.
hooks
headroomlabs-ai/headroom 79,508
Maintain cicero?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.