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/jam4fox99/market-map/agents-mdgit clone --depth 1 https://github.com/jam4fox99/market-mapWrote 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/jam4fox99/market-map/agents-md)<a href="https://agentmods.dev/instructions/jam4fox99/market-map/agents-md"><img src="https://agentmods.dev/badge/instructions/jam4fox99/market-map/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.00182 | $0.00182 |
| Opus 5 | $0.00091 | $0.00091 |
| Sonnet 5 | $0.00036 | $0.00036 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
market-map 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.
What it actually says
Repository instructions
- Treat
BUILD_SPEC.md(or the original market-analysis build specification while the canonical copy is being prepared) as the authoritative product contract. - Preserve
.envbyte-for-byte. Never print, copy, rename, overwrite, commit, or pass its values to unrelated processes. - Build fixture-first. Do not make live provider calls until the deterministic demo and test gates pass.
- Never inspect or retrieve the validation holdout before a discovery run is frozen and checksum-verified.
- Keep business logic under
packages/; delivery surfaces underapps/stay thin. - Keep changes inside your assigned paths when working in parallel, and do not revert another contributor's work.
- Use deterministic IDs, canonical JSON, exact evidence spans, explicit UTC cutoffs, and conservative entity-resolution abstention.
- Put post-P0 scope ideas in
docs/follow_up_backlog.md.
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 · 12 lines · 182 tokens per session scan A b87b11f15eb4
market-map AGENTS.md is an instructions file published in the GitHub repository jam4fox99/market-map (0 stars, last pushed 1mo ago), licensed MIT. It adds 182 tokens to every session, about $0.0009 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 instructions, from other repositories
full-stack-ai-agent-template CLAUDE.md
Instructions for vstorm-co/full-stack-ai-agent-template, covering claude.md, project overview, commands, install dependencies and run tests.
full-stack-ai-agent-template AGENTS.md
Instructions for vstorm-co/full-stack-ai-agent-template, covering agents.md, project overview, commands, cli and architecture.
tracecat AGENTS.md
AGENTS.md instructions for TracecatHQ/tracecat, covering tracecat agent notes, path-specific notes, repo map, fargate deployment notes and setup and verification.
tracecat CLAUDE.md
Claude Code instructions for TracecatHQ/tracecat, a project described as: Open-source security automation platform for teams and AI agents.
e-commerce-agents CLAUDE.md
Instructions for nitin27may/e-commerce-agents, covering claude.md, what this is, working artifacts location, key commands and start everything from scratch (one command).
OpenNotebookLM AGENTS.md
Instructions for tom1030507/OpenNotebookLM, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.