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/thesammykins/context-mcp/agents-mdgit clone --depth 1 https://github.com/thesammykins/context-mcpWrote 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/thesammykins/context-mcp/agents-md)<a href="https://agentmods.dev/instructions/thesammykins/context-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/thesammykins/context-mcp/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.00495 | $0.00495 |
| Opus 5 | $0.00247 | $0.00247 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
context-mcp 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 4d 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
AGENTS.md
Build Commands
npm run build- Clean and build productionnpm run build:dev- Development build (no clean)npm run dev- Watch mode for developmentnpm run test- Run all testsnpm run test:watch- Watch testsnpm run test -- src/__tests__/tools/get-context.test.ts- Run single test filenpm run lint- Currently no ESLint config
Code Style Guidelines
- TypeScript with strict mode enabled
- ES2022 target, Node16 modules
- Use
.jsextensions for imports (ESM) - Vitest for testing with globals enabled
- Test files in
src/__tests__/with.test.tssuffix - Use Zod for runtime validation
- Error handling with try/catch, console.error for logging
- Follow existing patterns: interfaces in types.ts, tool functions return handlers
- Database operations use better-sqlite3 with proper cleanup in afterEach
Agent Progress Tool Usage
Workflow Pattern
- Search:
search_logs(projectId, query)- discover previous work - Context:
get_context(projectId, id, includeFull=true)- understand implementation - Log:
log_progress(projectId, title, content, tags, agentId)- record your work
When to Use
- Before starting: Always search to avoid duplication
- After completing: Log significant work (features, refactoring, infrastructure, tests)
- Don't log: Minor tweaks, temporary code, personal notes
Best Practices
- Use repository names as projectIds (
web-app,mobile-app) - Be specific in content: exact files, libraries, approaches
- 3-5 relevant tags max: technology + feature + type
- Reference related work when building on others' contributions
Commit Guidelines
- Use conventional commits:
feat:,fix:,chore:,docs:,style:,refactor:,perf:,test: feat!triggers major version bump,feat:triggers minor,fix:triggers patch- Commits without conventional types don't trigger releases
- All commits appear in changelog unless marked hidden in release-please config
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.
- 4d ago First seen · 45 lines · 495 tokens per session scan A 0ed67da2147c
context-mcp AGENTS.md is an instructions file published in the GitHub repository thesammykins/context-mcp (0 stars, last pushed 9mo ago), licensed MIT. It adds 495 tokens to every session, about $0.0025 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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.
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.
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).