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/agentalabs/agenta-plugin/claude-mdgit clone --depth 1 https://github.com/agentalabs/agenta-pluginWrote 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/agentalabs/agenta-plugin/claude-md)<a href="https://agentmods.dev/instructions/agentalabs/agenta-plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/agentalabs/agenta-plugin/claude-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.00719 | $0.00719 |
| Opus 5 | $0.00360 | $0.00360 |
| Sonnet 5 | $0.00144 | $0.00144 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
agenta-plugin CLAUDE.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 3d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agenta Plugin — Agent Instructions
This project uses Agenta Plugin. The .mcp.json file configures which MCP servers are available as tools.
Tool Usage Priority
When completing tasks, use the best tool available — native Claude Code tools are often sufficient:
| Need | Best tool | When to escalate |
|---|---|---|
| Look up library docs | Context7 or mcpdoc | — |
| Simple web search | WebSearch (native) | Omnisearch for multi-engine research |
| Fetch a URL | WebFetch (native) | Crawl4AI for anti-bot sites, Puppeteer for JS-rendered pages |
| Read/write/edit files | Read, Write, Edit (native) | — |
| Search file contents | Grep, Glob (native) | — |
| Store structured data | SQLite, Supabase, or Postgres | — |
| Store embeddings | Qdrant or Claude Context | — |
| Track entities & relations | MemoryGraph | — |
| Run untrusted code | E2B or Daytona sandbox | — |
| Scrape web pages | Crawl4AI | Puppeteer for JS-rendered pages |
| Search academic papers | Consensus | — |
| Manage context window | Context Mode | — |
| Persistent cross-session memory | Memsearch | — |
| Ingest sources into KB | Skill Seekers | — |
Important
Always clarify with the user if something is unclear before proceeding.
Knowledge Base Maintenance
If this project maintains a knowledge base, follow these patterns:
Source registry
Maintain a source registry in SQLite tracking each data source:
- Source name, type (rss, api, webpage, file, database), URL/path
- Sync schedule (daily, weekly, on-demand)
- Last sync timestamp and content hash
- Status (active, error, disabled)
Incremental sync
On each maintenance run:
- Query the source registry for sources due for sync
- For each source: fetch content, compare hash to last known hash
- Skip unchanged sources entirely
- For changed sources: chunk, embed, deduplicate (similarity > 0.95 = skip), upsert
- Update the registry with new timestamp and hash
- Log: sources_checked, items_added, items_skipped, errors
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.
- 3d ago First seen · 78 lines · 719 tokens per session scan A 995d6f15215e
agenta-plugin CLAUDE.md is an instructions file published in the GitHub repository agentalabs/agenta-plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 719 tokens to every session, about $0.0036 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.