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.
npx skills add existential-birds/beagle --skill quick-plangit clone --depth 1 https://github.com/existential-birds/beagleWrote 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/skills/existential-birds/beagle/quick-plan)<a href="https://agentmods.dev/skills/existential-birds/beagle/quick-plan"><img src="https://agentmods.dev/badge/skills/existential-birds/beagle/quick-plan/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/skills/existential-birds/beagle/quick-plan"><img src="https://agentmods.dev/badge/skills/existential-birds/beagle/quick-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 57 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 198 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00230 | $0.04654 |
| Opus 5.5 | $0.00092 | $0.01862 |
| Sonnet 5.5 | $0.00046 | $0.00931 |
| Haiku 4.5 | $0.00023 | $0.00465 |
Grade A, and why
quick-plan 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Plan: Conversation Into Implementation Plan
Turn the work already discussed in this session into the same comprehensive, TDD-driven implementation plan write-plan produces — but without a spec. An engineer (or downstream agent) can execute it task-by-task without re-deriving intent.
The output is a single markdown plan at .beagle/plans/<slug>/plan.md. The plan captures HOW — file structure, task decomposition, exact tests, exact commands. Because there is no spec, quick-plan also captures the WHAT and WHY inside the plan, in an Intent header it synthesizes from the conversation and verifies before locking.
What Replaces the Spec
write-plan leans on a reviewed spec for three things. quick-plan reconstructs each, because skipping them is how plans bake in unexamined assumptions:
| The spec gives write-plan… | quick-plan reconstructs it from… |
|---|---|
| WHAT / WHY (requirements, core value, out-of-scope) | The conversation — what the user has been asking for, correcting, and ruling out this session — distilled into an Intent Brief. |
| Key Decisions (vetted architectural choices) | Fanout domain-expert subagents that recommend an approach grounded in this codebase's real patterns and the stack's idioms. |
| Reference Points (analogous existing code) | The same fanout subagents, returning file:line analogs the plan mirrors. |
| A human-reviewed gate | A gap check: proceed silently when the conversation is unambiguous; ask the user targeted questions only where intent has real holes. |
The spec is a contract written before planning. quick-plan writes that contract during planning, from cheaper signals, and confirms only the load-bearing parts with the user. Everything downstream of the Intent Brief — task decomposition, TDD discipline, the recoverability test, the self-review gates — is identical to write-plan. Same output, different front-half.
Workflow
Complete these steps in order:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 219 lines · 230 tokens per session scan A 40fb78bb11fe
quick-plan is a skill published in the GitHub repository existential-birds/beagle (84 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 230 tokens to every session and 4,654 once invoked, about $0.0009 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 skills, from other repositories
Unit Test Scaffold (Python/pytest)
Generate Python/pytest unit test skeletons from specifications.
golang-testing
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
django-testing
Django testing discipline — TDD workflow for Django/DRF (RED-GREEN-REFACTOR against models, views, serializers, permissions), pytest-django and factory patterns, database and transaction handling in tests, API client testing, AND the verification gates a Django change must pass before it ships (migrations check…
code-review
Perform a structured code review of changes, checking for correctness, style, tests, and potential issues.
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
react-web
React web development with hooks, React Query, Zustand.