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 rules/thebnbrkr/agora-code/agoragit clone --depth 1 https://github.com/thebnbrkr/agora-codeWhat 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.00455 | $0.00455 |
| Opus 5 | $0.00228 | $0.00228 |
| Sonnet 5 | $0.00091 | $0.00091 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
agora 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 2d 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.
What it actually says
agora-code — Agent Instructions
Always do this
- Before reading any file over ~200 lines, run
agora-code summarize <file>first - At session start, run
agora-code injectto load previous session context - When you discover something non-obvious, run
agora-code learn "<finding>" - Before starting any task, run
agora-code recall "<query>"to check if it's been solved before
Tool reference
| Command | When to use |
|---|---|
agora-code inject |
Session start — loads goal, hypothesis, last steps |
agora-code summarize <file> |
Before reading large files — uses DB cache when same commit |
agora-code learn "<text>" |
You find a bug, gotcha, or decision worth remembering |
agora-code recall "<query>" |
Before starting work — check if it's been solved before |
agora-code checkpoint --goal "..." |
After completing a meaningful step |
agora-code status |
Current session + DB path and row counts |
agora-code memory |
Dump all DB (sessions, learnings, snapshots, symbols); add --verbose for AST/code blocks |
agora-code list-sessions / list-learnings / list-snapshots / list-symbols / list-file-changes / list-api-calls |
View each DB table without SQL |
agora-code index <file> |
Re-index file into DB (hooks do this on edit; use if needed manually) |
agora-code scan . |
To discover API routes in the codebase |
Session lifecycle
Start → agora-code inject
Working → agora-code summarize <file> before reading large files
Finding → agora-code learn "<what you found>"
Step done → agora-code checkpoint --goal "..." --action "..."
All done → agora-code complete --summary "..."
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.
- 2d ago First seen · 40 lines · 455 tokens per session scan A 3263f96dcfcc
agora is a cursor rule published in the GitHub repository thebnbrkr/agora-code (46 stars, last pushed 13d ago), licensed Apache-2.0. It adds 455 tokens to every session, about $0.0023 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.