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.
git clone --depth 1 https://github.com/MTimma/knowerageWrote 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/rules/mtimma/knowerage/knowerage-analysis)<a href="https://agentmods.dev/rules/mtimma/knowerage/knowerage-analysis"><img src="https://agentmods.dev/badge/rules/mtimma/knowerage/knowerage-analysis/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/mtimma/knowerage/knowerage-analysis"><img src="https://agentmods.dev/badge/rules/mtimma/knowerage/knowerage-analysis.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00363 | $0.00363 |
| Opus 5.5 | $0.00145 | $0.00145 |
| Sonnet 5.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 1mo 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.
- 1mo 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 5mo ago), licensed MIT. It adds 363 tokens to every session, about $0.0015 per session on Opus 5.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
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
javascript-expert-performance
Profile first. Measure before and after. Never optimize without data.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
5-bug-finder
APPLY WHEN investigating a bug.