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/manojmallick/sigmap/agents-mdgit clone --depth 1 https://github.com/manojmallick/sigmapWrote 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/manojmallick/sigmap/agents-md)<a href="https://agentmods.dev/instructions/manojmallick/sigmap/agents-md"><img src="https://agentmods.dev/badge/instructions/manojmallick/sigmap/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.15631 | $0.15631 |
| Opus 5 | $0.07816 | $0.07816 |
| Sonnet 5 | $0.03126 | $0.03126 |
| Haiku 4.5 | $0.01563 | $0.01563 |
Grade A, and why
sigmap 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 today.
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 — 1,122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SigMap — AGENTS.md
Instructions for Codex-style agents working in this repository.
Append Strategy (Required)
When writing generated signature content, never overwrite human-written notes
above the auto-generated marker. Everything above the marker (like these notes)
is preserved verbatim; everything below it is regenerated by gen-context.js.
Each generated context file carries one canonical SigMap commands guidance block
(emitted from formatOutput, identical across every context file). Signatures
keep their full parameter lists and return types — the token budget drops whole
low-priority files rather than collapsing signatures to bare line anchors.
Auto-generated signatures
Code signatures
SigMap commands
| When | Command |
|---|---|
| Before answering a question about code | sigmap ask "<your question>" |
| To rank files by topic | sigmap --query "<topic>" |
| After changing config or source dirs | sigmap validate |
| To verify an AI answer is grounded | sigmap judge --response <file> |
Always run sigmap ask (or sigmap --query) before searching for files relevant to a task.
todos
gen-context.js:22350 # TODO: s');
changes (last 5 commits — 10 days ago)
src/graph/builder.js ~extractFileDeps
src/retrieval/ranker.js ~_buildSigIndexFromCache ~_enrichSigIndexFromStrategy
gen-context.js +whose +extractClassMembers +stripComments +maskCode
src/extractors/javascript.js +whose +extractClassMembers ~whose ~extractClassMembers
src/extractors/scan.js +stripComments +maskCode +readBalanced
src/extractors/typescript.js +extractClassMembers ~extractClassMembers ~extract ~extractBlock
src/verify/arity.js +exist +cleanSig +parseParams +buildArityIndex
src/verify/hallucination-guard.js +whose ~buildSymbolSet ~verify
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.
- today Changed · -285 lines · +1,098 tokens per session 18cb10caea84
- 4d ago First seen · 1,407 lines · 14,533 tokens per session scan A 6d682e1399a0
sigmap AGENTS.md is an instructions file published in the GitHub repository manojmallick/sigmap (624 stars, last pushed yesterday), licensed MIT. It adds 15,631 tokens to every session, about $0.0782 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
llm-ide-rules react.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering react, mock data, react hook form and styling.
obsidian-mcp-rs CLAUDE.md
Instructions for MrRefactoring/obsidian-mcp-rs, covering claude.md, commands, build / run, tests and lint gates enforced by ci (.github/workflows/ci.yml).
llm-ide-rules typescript.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering typescript and dates & times.
carrymem CLAUDE.md
Instructions for lulin70/carrymem, covering claude.md — carrymem ai 协作指引, 项目概述, 安装与构建, 用户安装（已发布到 pypi） and 完整功能安装.
llm-ide-rules python-route-tests.instructions.md
Instructions for iloveitaly/llm-ide-rules, a project described as: Centralized LLM prompt instructions for Copilot and Cursor, including scripts to convert and sync rules for Python, React, Shell, and TypeScript. Designed for rapid reuse and contribution across projects.
llm-ide-rules shell.instructions.md
Instructions for iloveitaly/llm-ide-rules, a project described as: Centralized LLM prompt instructions for Copilot and Cursor, including scripts to convert and sync rules for Python, React, Shell, and TypeScript. Designed for rapid reuse and contribution across projects.