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/snowdreamtech/frpWrote 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/snowdreamtech/frp/speckit_speckit.clarify)<a href="https://agentmods.dev/rules/snowdreamtech/frp/speckit_speckit.clarify"><img src="https://agentmods.dev/badge/rules/snowdreamtech/frp/speckit_speckit.clarify.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.00000 | $0.00069 |
| Opus 5 | $0.00000 | $0.00034 |
| Sonnet 5 | $0.00000 | $0.00014 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
speckit_speckit.clarify 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 2d 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:
- speckit_speckit.clarify — 100% identical, 0 lines differ
What it actually says
Speckit Workflow: speckit.clarify
When the user asks to run /speckit.clarify, you MUST read .specify/commands/speckit.clarify.md and follow its instructions exactly.
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.
- 2d ago First seen · 9 lines · 69 tokens per session scan A c46e34a36dcc
speckit_speckit.clarify is a cursor rule published in the GitHub repository snowdreamtech/frp (908 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 69 tokens. 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-05.
Other cursor rules, from other repositories
020-flask
Flask API Gateway conventions for LMForge.
env-credentials
Handle missing environment variables or credentials by sourcing .env files.
tech-debt-prevention
Tech debt prevention patterns with consistency enforcement, code quality gates, and architectural governance.
architectural-and-structural-rules
The project follows a layered architecture with clear separation of concerns.
docker-deployment
Complete Docker containerization, production deployment, and monitoring patterns for POS System.
tanstack-react-router_setup-and-architecture
TanStack Router: Setup and Architecture.