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/Zwanan-github/agent-templateWrote 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/zwanan-github/agent-template/project)<a href="https://agentmods.dev/rules/zwanan-github/agent-template/project"><img src="https://agentmods.dev/badge/rules/zwanan-github/agent-template/project/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/zwanan-github/agent-template/project"><img src="https://agentmods.dev/badge/rules/zwanan-github/agent-template/project.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.00149 | $0.00149 |
| Opus 5.5 | $0.00060 | $0.00060 |
| Sonnet 5.5 | $0.00030 | $0.00030 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
project 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 1mo 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
Follow AGENTS.md as the source of truth for this repository.
For feature work:
- Read
AGENTS.mdbefore editing. - Create or update a feature spec under
specs/features/when required byAGENTS.md. - Plan before implementation.
- Inspect existing code and test style before implementation.
- Follow the project's current test framework and conventions.
- Ask if the development/test environment is missing or unclear; propose Docker only when configured or approved.
- Keep changes scoped.
- Run relevant tests.
- Summarize changed files, test results, and remaining risks.
Useful workflow prompts live under agent-workflow/skills/.
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.
- 1mo ago First seen · 21 lines · 149 tokens per session scan A 17d5cd18c560
project is a cursor rule published in the GitHub repository Zwanan-github/agent-template (2 stars, last pushed 3mo ago), licensed MIT. It adds 149 tokens to every session, about $0.0006 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
trueforge-ui-slots
Every newly created or newly JSX-bearing component in @truefoundry/trueforge-ui MUST be host-overridable through the slots system. Do not hard-import leaf UI into layouts/containers when a slot exists (or should exist).
styles-rem-not-px
Prefer rem over px for UI lengths (1rem = 16px).
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.