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/mtimma/knowerage/knowerage-analysisgit clone --depth 1 https://github.com/MTimma/knowerageWhat 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.00363 | $0.00363 |
| Opus 5 | $0.00181 | $0.00181 |
| Sonnet 5 | $0.00073 | $0.00073 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
knowerage-analysis 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
Knowerage Analysis Workflow
If Knowerage MCP tools appear in your available tools, the user has opted in: use them for any task that analyzes, documents, or explains legacy/source files in this workspace. Do not bypass Knowerage by writing knowerage/analysis/**/*.md with generic file-edit tools only, and never hand-edit knowerage/registry.json.
When analyzing legacy code (Java, XML, or other source files):
- Create analysis — Use
knowerage_create_or_update_docto create an.mdfile with YAML frontmatter (source_file,covered_lines,analysis_date). - Reconcile — Call
knowerage_reconcile_recordafter creating or updating an analysis file (required every time). - Record coverage —
knowerage_reconcile_recordupdatesknowerage/registry.json(no manual append needed).
Registry inventory — To see every analysis↔source mapping, covered line ranges, and freshness in one response (same structure as registry.json), call knowerage_list_registry instead of reading the file manually.
"Analyze X" implies full workflow — create analysis, reconcile, and record coverage. No need for the user to say "record coverage" or "use the MCP" explicitly.
Repos without this rule — Users who only installed the MCP should add the same guidance to their client’s user-level agent rules (if supported) or add a project rules file using a path and format their MCP host documents (this repo uses .cursor/rules/ as an example).
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 · 21 lines · 363 tokens per session scan A 314d7142bdb4
knowerage-analysis is a cursor rule published in the GitHub repository MTimma/knowerage (3 stars, last pushed 4mo ago), licensed MIT. It adds 363 tokens to every session, about $0.0018 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-31.
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
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.
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.