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/Hundia/autospecWrote 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/hundia/autospec/execute-ticket)<a href="https://agentmods.dev/rules/hundia/autospec/execute-ticket"><img src="https://agentmods.dev/badge/rules/hundia/autospec/execute-ticket/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/hundia/autospec/execute-ticket"><img src="https://agentmods.dev/badge/rules/hundia/autospec/execute-ticket.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.00000 | $0.00660 |
| Opus 5.5 | $0.00000 | $0.00264 |
| Sonnet 5.5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
execute-ticket 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute Ticket
Follow this procedure to implement a single ticket from the backlog.
Step 1: Locate the Ticket
- Open
specs/backlog.md - Find the ticket by number (e.g.,
16.3) - Read the ticket description, acceptance criteria, and dependencies
- If the ticket has unresolved dependencies, stop and report them
Step 2: Read Context
Before writing any code, read the relevant documentation:
- Always read:
specs/backlog.md(full sprint context) - Feature work: the relevant spec file (
specs/02-06,specs/10) - Bug fix: reproduce the bug first, understand the root cause
- Viewer changes:
docs/viewer/for component patterns - CLI changes:
docs/cli/for command structure and patterns - Architecture questions:
specs/04-architecture.md
Step 3: Update Status
In specs/backlog.md, change the ticket status:
🔲 → 🔄
This signals that work has started.
Step 4: Implement
Follow these patterns during implementation:
- TypeScript strict — no
anytypes, use Zod for validation - Repository → Service → Controller layering
- Frontend: React components with Tailwind, Zustand for state
- Tests: write or update tests alongside the implementation
- Small commits: commit after each logical unit of work
File Organization
- CLI source:
cli/src/ - Viewer source:
viewer/src/ - Specs:
specs/ - Docs:
docs/
Step 5: QA Verification
Scale QA to the type of change:
| Change Type | QA Steps |
|---|---|
| Bug fix | Reproduce → fix → verify the fix → run related tests |
| CLI change | cd cli && npm run build && npm test |
| Viewer change | cd viewer && npm run build + visual check |
| Docs/config only | Review for accuracy — no build needed |
| New feature | Full test suite + write new test cases |
Step 6: Update Documentation
If your change affects behavior visible to users or developers:
- Update the relevant
docs/file(s) - If no doc file exists for your subsystem, create one in
docs/<subsystem>/ - Keep docs concise — focus on what changed and why
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 · 93 lines · 0 tokens per session scan A 9cf77105f0af
execute-ticket is a cursor rule published in the GitHub repository Hundia/autospec (4 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 660 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-03.
Other cursor rules, from other repositories
issue-harvester
Maintain exhaustive Slate/Plate issue-closure ledgers from current issue, PR, test and local proof evidence.
project-conventions
Core project conventions for the Uniqlo Sales Alerter.
delivery-quality-gates
Required delivery flow from development through QA automation and evidence.
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.