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 agents/luismiglezmohino/ai-dev-agents/project-contextgit clone --depth 1 https://github.com/luismiglezmohino/ai-dev-agentsWrote 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/agents/luismiglezmohino/ai-dev-agents/project-context)<a href="https://agentmods.dev/agents/luismiglezmohino/ai-dev-agents/project-context"><img src="https://agentmods.dev/badge/agents/luismiglezmohino/ai-dev-agents/project-context.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.00007 | $0.00269 |
| Opus 5 | $0.00003 | $0.00134 |
| Sonnet 5 | $0.00001 | $0.00054 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
project-context 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 5d 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
PROJECT CONTEXT
Domain
Describe the business domain in 1-2 lines.
Users
End-user profile. Roles, special needs, usage context.
Constraints
One constraint per line. Only the NON-negotiable ones.
- License:
- Privacy:
- Accessibility:
- Performance:
Technical Decisions
Decisions already made that agents must respect. Format: decision — reason.
Artifact Paths
Paths where each agent should create/find its artifacts.
- Docs:
docs/ - ADRs:
docs/adrs/ADR-XXX-title.md - Specs:
docs/specs/FEAT-XXX-title.md - Stories:
docs/stories/US-XXX-title.md - Guides:
.ai/docs/
Limits
API rate limits, budget, server capacity.
Commands
# Test:
# Lint:
# Build:
Learn & Persist
If you detect a recurring pattern (3+ occurrences), evaluate it:
- Good pattern → propose adding it to this file under Technical Decisions
- Anti-pattern → propose a constraint or restriction that prevents it
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.
- 5d ago First seen · 56 lines · 7 tokens per session scan A ec4ea33da13a
project-context is an agent published in the GitHub repository luismiglezmohino/ai-dev-agents (3 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 269 once invoked, about $0.0000 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 agents, from other repositories
architect
Rules & governance catalog for AI/LLM-assisted engineering — architecture, security, and change discipline as machine-readable rules.
code-reviewer
Rules & governance catalog for AI/LLM-assisted engineering — architecture, security, and change discipline as machine-readable rules.
devops
Rules & governance catalog for AI/LLM-assisted engineering — architecture, security, and change discipline as machine-readable rules.
implementer
Rules & governance catalog for AI/LLM-assisted engineering — architecture, security, and change discipline as machine-readable rules.
orchestrator
Rules & governance catalog for AI/LLM-assisted engineering — architecture, security, and change discipline as machine-readable rules.
perf-optimizer
Rules & governance catalog for AI/LLM-assisted engineering — architecture, security, and change discipline as machine-readable rules.