knowerage AGENTS.md

Project instructions for Knowerage, an MCP server for analysing and documenting source files, including legacy code. They require creating analysis documents and reconciling their coverage through Knowerage tools.

In plain words
What is it for?
Use them when analysing, explaining, or documenting legacy or source files in the Knowerage repository, particularly when recording which files and lines have been covered.
Why use it?
They prevent analysis records from becoming inconsistent with the repository's registry. They also ensure legacy-code explanations follow the project's required documentation process.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/mtimma/knowerage/agents-md
Clone the repo
git clone --depth 1 https://github.com/MTimma/knowerage

Made for: Codex, OpenCode.

Per session 262 This file is loaded in full into every session.
When invoked 262 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00262 $0.00262
Opus 5 $0.00131 $0.00131
Sonnet 5 $0.00052 $0.00052
Haiku 4.5 $0.00026 $0.00026

Measured 2d ago against content hash 90d014f488f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

knowerage 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 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.

AGENTS.md · 14 lines

What it actually says

Agent instructions — Knowerage

This repository ships the Knowerage MCP server. When Knowerage MCP tools are available in your session, use them for any task that analyzes, documents, or explains legacy or 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):

  1. Create analysisknowerage_create_or_update_doc with YAML frontmatter (source_file, covered_lines, analysis_date).
  2. Reconcileknowerage_reconcile_record after every create or update to that analysis file (required).
  3. Coverage — Reconcile updates knowerage/registry.json; no manual registry edits.

For a full registry snapshot (same shape as registry.json), use knowerage_list_registry instead of opening the file by hand. “Analyze X” means the full workflow above; the user does not need to say “record coverage” or “use the MCP.”

More detail: INSTRUCTIONS.md, contracts/contracts.md.

Changes

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.

  1. 2d ago First seen · 14 lines · 262 tokens per session scan A 90d014f488f8

Subscribe to this mod's changes

knowerage AGENTS.md is an instructions file published in the GitHub repository MTimma/knowerage (3 stars, last pushed 4mo ago), licensed MIT. It adds 262 tokens to every session, about $0.0013 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.

Related

Other instructions, from other repositories

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens