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/mablanco/pricegrabWrote 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/mablanco/pricegrab/specify-rules)<a href="https://agentmods.dev/rules/mablanco/pricegrab/specify-rules"><img src="https://agentmods.dev/badge/rules/mablanco/pricegrab/specify-rules/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/mablanco/pricegrab/specify-rules"><img src="https://agentmods.dev/badge/rules/mablanco/pricegrab/specify-rules.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.00193 | $0.00193 |
| Opus 5.5 | $0.00077 | $0.00077 |
| Sonnet 5.5 | $0.00039 | $0.00039 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
specify-rules 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
For additional context about the active feature, technologies, project structure, shell commands, and other important information:
- Read the active feature pointer:
.specify/feature.json(currentlyspecs/008-richer-result-card). - Open the active plan:
specs/008-richer-result-card/plan.md(and siblingspec.md,research.md,tasks.md). - For shipped state and the product backlog, read
docs/project-status.md.
When feature.json is missing or stale after a release, default to the latest
specs/<nnn-*>/ directory and confirm with Marco before starting new work.
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 · 20 lines · 193 tokens per session scan A 3e4568ae5f9f
specify-rules is a cursor rule published in the GitHub repository mablanco/pricegrab (11 stars, last pushed 1mo ago), licensed MIT. It adds 193 tokens to every session, about $0.0008 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-30.
Other cursor rules, from other repositories
compose-accessibility
Compose accessibility rules for TalkBack — icons, headings, Canvas, live regions, focus, modals, and attribute preservation.
compose-coroutines
Compose scroll/coroutine patterns — prevent programmatic scroll from being mistaken for user scroll, cancellation-safe flag resets.
testing-conventions
Testing conventions — JUnit 4, Kotest property tests, instrumented tests, what to test when.
ios-viewmodel
ViewModels conform to ObservableObject and expose state via @Published properties.
compose-ui
Compose UI conventions — Material 3, recomposition optimization, Compose-only UI, theming.
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.