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.
git clone --depth 1 https://github.com/Jacoby6000/SmithplatesWrote 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/rules/jacoby6000/smithplates/agents-md)<a href="https://agentmods.dev/rules/jacoby6000/smithplates/agents-md"><img src="https://agentmods.dev/badge/rules/jacoby6000/smithplates/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/jacoby6000/smithplates/agents-md"><img src="https://agentmods.dev/badge/rules/jacoby6000/smithplates/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00463 | $0.00463 |
| Opus 5.5 | $0.00185 | $0.00185 |
| Sonnet 5.5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
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 2mo 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
AGENTS.md
Every repository should have an AGENTS.md at its root — the predictable place
for agent-facing context that would clutter a README (build/test/lint commands,
conventions, architecture decisions, gotchas). Keep it separate from README.md,
which stays focused on human contributors. See https://agents.md/.
Maintain it as you work
Treat AGENTS.md as living documentation and update it regularly, without being
asked, as the codebase grows:
- Record decision points: when you make or discover a non-obvious choice
(an approach taken, a constraint, a rejected alternative and why), capture it
so future agents don't relitigate it. This complements in-code
DESNOTEs — durable, cross-cutting decisions belong here. - Keep commands current: build, test, lint/format, and run commands an agent needs. Agents will execute listed checks, so they must be accurate.
- Capture conventions and gotchas: project structure, naming, and anything strange or surprising about the environment.
- If a repository has no
AGENTS.md, create one when you begin substantive work.
Detailed reference docs (.ai-doc-reference/)
Keep AGENTS.md lean. For detailed information that is valuable but too large or
specialized to keep in context at all times, write a dedicated document under
.ai-doc-reference/ that agents fetch on demand. Use this for things like
persistent CAD documents, schemas/contracts, deep design write-ups, runbooks,
and data-model references.
- Produce thorough, self-contained docs there as the codebase grows — favor detail over brevity, since these are loaded only when needed.
- From
AGENTS.md, link to each reference doc with a one-line description of what it contains and when to read it, so agents know what is available to pull in without loading it eagerly.
Monorepos
Use nested AGENTS.md files inside subprojects/packages. The file nearest the
edited code wins; an explicit user instruction overrides any AGENTS.md.
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.
- 2mo ago First seen · 46 lines · 463 tokens per session scan A 5f43d7310b6e
agents-md is a cursor rule published in the GitHub repository Jacoby6000/Smithplates (2 stars, last pushed 20d ago), licensed MIT. It adds 463 tokens to every session, about $0.0019 per session on Opus 5.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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.