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/alexpialetski/doccraftWrote 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/alexpialetski/doccraft/planning-queue)<a href="https://agentmods.dev/rules/alexpialetski/doccraft/planning-queue"><img src="https://agentmods.dev/badge/rules/alexpialetski/doccraft/planning-queue/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/alexpialetski/doccraft/planning-queue"><img src="https://agentmods.dev/badge/rules/alexpialetski/doccraft/planning-queue.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.00253 |
| Opus 5.5 | $0.00000 | $0.00101 |
| Sonnet 5.5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
planning-queue 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
Managed by doccraft —
doccraft updateregenerates this file. Local edits will be overwritten. Seedoccraft.jsonto override project-specific vocabulary and paths without touching this file.
Working queue
When editing docs/queue.md:
- The editorial process (ordering rules, dependency precedence, parallel
waves) lives in the
doccraft-queue-auditskill. Follow that skill rather than reinventing. - Keep the Suggested order table in sync with story
urgency/impactwhen you reprioritise.docs/backlog.mdowns the full P-tier tables and Status column. - Rows must link to existing files under
docs/stories/; add a story file (and a row in the backlog's Story files table) when introducing a new queued item. - After any
depends_onedit or meaningful queue reorder, invokedoccraft-queue-auditin the same turn to keep the graph and tables consistent.
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 · 25 lines · 0 tokens per session scan A f25bf165f643
planning-queue is a cursor rule published in the GitHub repository alexpialetski/doccraft (4 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 253 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-08-31.
Other cursor rules, from other repositories
archgate-governance
Archgate ADR governance — enforces architecture decision records.
swamr-orchestrator
Swamr Orchestrator — autonomous agent swarm that builds entire projects. Invoke with @swamr-orchestrator followed by what you want built. Decomposes into tasks, selects specialist agents, runs dev↔QA loops, and delivers production-ready code.
prompt-to-asset
Asset generation — route, rewrite, generate, validate. Never send transparency requests to Imagen/Gemini.
solana-transaction-safety
Safe Solana transaction submission patterns using Helius Sender.
swamr-state-manager
Swamr State Manager — tracks task progress, manages the execution pipeline, handles retries and escalation. Maintains swamr/state.json as the single source of truth for swarm progress.
read-xlsx
Reading, writing, diffing, and repairing spreadsheets (.xlsx) for AI agents via the xfa MCP server.