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/proyecto26/projectx/agents-mdgit clone --depth 1 https://github.com/proyecto26/projectxWhat 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.01313 | $0.01313 |
| Opus 5 | $0.00656 | $0.00656 |
| Sonnet 5 | $0.00263 | $0.00263 |
| Haiku 4.5 | $0.00131 | $0.00131 |
Grade A, and why
projectx 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ProjectX
Full-stack event-driven application using Temporal workflows and React Router v7.
Tech Stack
- Package Manager:
pnpm - Frontend: React 19, React Router v7, Vite, TailwindCSS (DaisyUI)
- Backend: NestJS, PostgreSQL
- Orchestration: Temporal
- Monorepo: Turbo
- Spec-Driven Development: OpenSpec
Documentation
Project Context
- Architecture Overview: docs/architecture/README.md - System design, event flows, and service breakdown.
- Database Schema: docs/backend/DATABASE.md - Prisma models and relationships.
- Payment Integration: docs/payment/README.md - Stripe integration guide.
- AI Search: docs/ai/search/IMAGE_SEARCH.md - Image search with CLIP + pgvector.
Domain Rules (Detailed Instructions)
- Frontend: docs/frontend/RULES.md (React Router, Components, Styling)
- Backend: docs/backend/RULES.md (NestJS, DTOs, Modules)
- Workflows: docs/backend/TEMPORAL.md (Workflow/Activity patterns, Determinism)
- Infrastructure: docs/architecture/INFRASTRUCTURE.md (Docker, Deployment)
OpenSpec Specifications
- Active Changes:
openspec/changes/- Work-in-progress feature specs and tasks. - Committed Specs:
openspec/specs/- Finalized specifications for implemented features.
Spec-Driven Development (OpenSpec)
Use OpenSpec to structure work around explicit specifications before writing code. This ensures AI agents have clear context and requirements.
Workflow
- Create a change:
/opsx:new <feature-name> - Plan artifacts:
/opsx:ff(fast-forward all) or/opsx:continue(step-by-step) - Implement tasks:
/opsx:apply - Verify implementation:
/opsx:verify - Archive completed work:
/opsx:archive
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 · 117 lines · 1,313 tokens per session scan A 9fb9861b6a6c
projectx AGENTS.md is an instructions file published in the GitHub repository proyecto26/projectx (83 stars, last pushed 4mo ago), licensed MIT. It adds 1,313 tokens to every session, about $0.0066 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
jido AGENTS.md
AGENTS.md instructions for agentjido/jido, covering agents.md - jido guide, intent, runtime baseline, commands and architecture snapshot.
cabloy CLAUDE.md
Instructions for cabloy/cabloy, covering cabloy monorepo guidance, repository identity, monorepo layout, preferred workflow and documentation boundary.
Better-Fullstack AGENTS.md
Instructions for Marve10s/Better-Fullstack, covering guidelines, web ui, workflow and bun.
Better-Fullstack CLAUDE.md
Instructions for Marve10s/Better-Fullstack, covering claude.md, code style, general preferences and picking the right models for workflows and subagents.
keryx CLAUDE.md
Instructions for actionhero/keryx, covering claude.md, project overview, monorepo structure, development environment and environment setup.
evjs AGENTS.md
Instructions for afx-team/evjs, covering agents.md, start here, source map, working rules and validation.