Borrowing it
Nothing to install: this file belongs to huvaxstra/AGNT. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/huvaxstra/AGNT/main/CLAUDE.mdgit clone --depth 1 https://github.com/huvaxstra/AGNTWrote 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/huvaxstra/agnt/claude-md)<a href="https://agentmods.dev/instructions/huvaxstra/agnt/claude-md"><img src="https://agentmods.dev/badge/instructions/huvaxstra/agnt/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.1 | $0.00450 | $0.00450 |
| Opus 5 | $0.00225 | $0.00225 |
| Sonnet 5 | $0.00090 | $0.00090 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
AGNT 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 6d 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
SpecAgnt — AI Agent Instructions
You are working on SpecAgnt, a project spec generator kit that produces AI-discoverable documentation from fill-in-the-blank templates.
Project Structure
SpecAgnt/
kit.md ← Main agent instructions (what AI agents read to use the kit)
engine.md ← Workflow orchestrator (7-step sequential workflow)
specagnt.json ← Auto-mode config (skip discovery questions)
knowledge/ ← Deep reference files (load on demand, never upfront)
base/ ← 30 fill-in-the-blank templates
examples/ ← Filled-in demo output for "TaskForge"
scripts/ ← Setup & validation tools
specbits/ ← 100 project idea JSON files
Key Rules
- Never modify
base/templates in place — they are the source of truth - Template count is 30 — do not add/remove without discussion
- Deleted files:
state-management.md,db-rollback.md,deploy-guide.mdwere merged into other templates - New files:
ai-integration.md,design-system-advanced.mdwere added - All references must stay in sync — kit.md, README.md, CHANGELOG.md, scripts, and base files cross-reference each other
- YAML frontmatter required on every template in
base/ - Placeholder format:
[...]or[AGENT: ...]— never leave empty brackets[]
When Editing
- Update README.md badge counts if template count changes
- Update CHANGELOG.md for any structural changes
- Run
bash scripts/validate-templates.shto verify consistency - Update kit.md Step 3/3.5/4/5 ordering if templates are added/removed
- Update scripts/validate.sh file number mappings if ordering changes
Testing
bash scripts/validate-templates.sh # Validates base/ template consistency
bash scripts/validate.sh [dir] # Validates generated docs cross-references
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.
- 6d ago First seen · 43 lines · 450 tokens per session scan A faa8a314011d
AGNT CLAUDE.md is an instructions file published in the GitHub repository huvaxstra/AGNT (5 stars, last pushed 3mo ago), licensed MIT. It adds 450 tokens to every session, about $0.0022 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).
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).
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.
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.