Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/5uck1ess/cicero/agents-mdgit clone --depth 1 https://github.com/5uck1ess/ciceroWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/5uck1ess/cicero/agents-md)<a href="https://agentmods.dev/instructions/5uck1ess/cicero/agents-md"><img src="https://agentmods.dev/badge/instructions/5uck1ess/cicero/agents-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00871 | $0.00871 |
| Opus 5 | $0.00436 | $0.00436 |
| Sonnet 5 | $0.00174 | $0.00174 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
cicero AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent guidance
This is the canonical project guidance for every coding agent. Provider-specific instruction files should import this file instead of copying it.
Product boundary
Cicero is a self-hosted voice layer for coding agents. Keep the voice,
transport, and lifecycle code independent of a specific brain. A brain is
currently pluggable through the internal TypeScript Brain contract, ACP, an
OpenAI-compatible endpoint, or a supported CLI adapter; do not describe the
private package as a stable third-party plugin SDK.
The default deployment is single-operator. Do not accidentally turn shared brain state, lanes, or transports into a multi-tenant contract.
Toolchain
- Use the Bun version pinned by
packageManagerinpackage.jsonand CI. - Use
bun install,bun run <script>,bun test, andbun x; do not add a second JavaScript package manager or lockfile. - Bun is the runtime, but existing
node:*standard-library imports are valid. - Keep dependencies pinned or bounded consistently with the existing lockfile.
- Do not add
dotenv; Bun loads environment files itself.
Verification
- Add focused
bun:testregressions for behavior changes and run them first. - Before a PR is ready, run
bun run typecheck, the fullbun test, andgit diff --check. tests/brain-claude-code-stream.test.tsis a live smoke test. It runs only withCICERO_LIVE_TESTS=1; never make normal CI depend on installed or authenticated agent CLIs.- If Python sidecars change, run their matching
unittest/native-contract checks with the Python and requirements files used by CI. - Hardware, credentials, acoustic behavior, and real remote providers need a labeled smoke test; do not present mocked CI as proof of those conditions.
Reliability and security invariants
- Every spawned process, timer, stream, socket, and signal handler needs one owner and a bounded cleanup path. Do not use process-wide kill patterns.
- Put absolute deadlines and size limits around subprocess, HTTP, and streaming work. A timeout must release or quarantine the owned resource before reuse.
- Fail closed when release is unconfirmed, but make stored failure latches retryable so recovery does not require a daemon restart.
- Preserve cancellation, one-shot context, and optional capabilities through every brain wrapper. Late work from an aborted or superseded turn must not publish output into a newer turn.
- Treat config, terminal output, provider bodies, model audio, and transport frames as untrusted input. Bound before retaining, parsing, or logging them.
- Never expose API keys, authorization headers, URL credentials, or query tokens in runtime errors, the application logger, or dashboard events. The ephemeral web credential is intentionally written to startup stdout; remember that a supervisor may retain it, and require a stable token for service deployments. Never commit real credentials, real voice-reference audio, or real user transcripts. Clearly synthetic secret markers are expected in redaction regressions.
- Keep local control surfaces authenticated and private storage symlink-safe.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 78 lines · 871 tokens per session scan A 5b3f14fb936d
cicero AGENTS.md is an instructions file published in the GitHub repository 5uck1ess/cicero (39 stars, last pushed 4d ago), licensed MIT. It adds 871 tokens to every session, about $0.0044 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
gini-agent AGENTS.md
AGENTS.md instructions for Open-Curiosity/gini-agent, covering gini agent instructions, shape, adrs, boundaries and branches.
Lody AGENTS.md
AGENTS.md instructions for LodyAI/Lody, covering repository guidelines, context maintenance, repository boundary, project map and checks and commits.
syncular AGENTS.md
Instructions for syncular/syncular, covering syncular agent instructions, doctrine (enforced), coding rules, prose rules for docs and voice.
gno AGENTS.md
AGENTS.md instructions for gmickel/gno, covering knowledge cutoff warning, apis - bun first!, must use bun, acceptable node:\ (no bun equivalent) and testing.
cognithor CLAUDE.md
Claude Code instructions for Alex8791-cyber/cognithor, covering claude.md, what this is, source layout, architecture in one paragraph and critical conventions.
ankaloop AGENTS.md
AGENTS.md instructions for tao12345666333/ankaloop, covering ankaloop project rules, project overview, code style, architecture patterns and agent behavior.