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/mslavov/shelly-forge/agents-mdgit clone --depth 1 https://github.com/mslavov/shelly-forgeWrote 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/mslavov/shelly-forge/agents-md)<a href="https://agentmods.dev/instructions/mslavov/shelly-forge/agents-md"><img src="https://agentmods.dev/badge/instructions/mslavov/shelly-forge/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.00387 | $0.00387 |
| Opus 5 | $0.00193 | $0.00193 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
shelly-forge 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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- shelly-forge CLAUDE.md — 94% identical, 7 lines differ
What it actually says
Documentation Usage Guidelines
CRITICAL: Framework-First Reading Order
📚 MANDATORY READING ORDER:
- FIRST: Read rules in
.agents/rules/- Framework rules and development guidelines - SECOND: Read
docs/INDEX.md- Documentation navigation hub - THIRD: Read your agent definition in
.agents/definitions/(if applicable) - THEN: Consult project-specific documentation as needed
Pre-Task Protocol
- Verify you've read the framework rules - All files in
.agents/rules/and INDEX.md are mandatory - Review relevant documentation - Use INDEX.md to find specific docs
- Check the Quick Task Lookup - Find the right documents for your task type
- Consult product documents from
docs/productas needed - Reference technical docs from
docs/techas needed
Post-Task Protocol
- Update the single authoritative source for any changed information
- Update cross-references if new relationships are created
- Move completed tasks from
.agents/tasks/in-progress/to.agents/tasks/done/ - Update
docs/INDEX.mdif new documents are created
Agent Commands
Agent commands are available as @ commands (e.g., @architect, @developer). Each command:
- Provides a brief role description
- Links to full documentation in
.agents/definitions/ - Assumes this AGENTS.md file has been read
See available commands in .cursor/rules/
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 · 33 lines · 387 tokens per session scan A d3e044c6909f
shelly-forge AGENTS.md is an instructions file published in the GitHub repository mslavov/shelly-forge (20 stars, last pushed 1y ago), licensed MIT. It adds 387 tokens to every session, about $0.0019 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-09-01.
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.