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 agentmods add skills/23ag1/completely/plannpx skills add 23ag1/completely --skill plangit clone --depth 1 https://github.com/23ag1/completelyWhat 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 | $0.00096 | $0.00813 |
| Opus 5 | $0.00048 | $0.00407 |
| Sonnet 5 | $0.00019 | $0.00163 |
| Haiku 4.5 | $0.00010 | $0.00081 |
Grade A, and why
completely: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 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.
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan into Beads directly. Do NOT write a PLAN.md / STATE.md — the plan lives in Beads.
Method (GSD methodology, Beads-first)
- Discover (socratic). Ask clarifying questions ONE at a time until the goal is unambiguous; offer 2–3 approaches with trade-offs; confirm scope. If a spec is already frozen, read it instead.
- Decompose into atomic tasks (2–5 min each). Each task MUST carry the worker-contract:
title(imperative),acceptance(observable/testable),design(approach/why),write_zone(exact files/globs),verify(the proof command),deps(other task keys). ~2–3 tasks per unit; split if a unit exceeds ~5 tasks or ~10 files (context budget). Also fill the context fields — the engine consumes them directly:read_context— the exact files/interfaces the worker must READ first but won't edit (contracts, schemas, neighbouring patterns). Injected verbatim into the worker's dispatch header, so a fresh context reads exactly this instead of guessing or scanning the tree.must_haves— the goal-backward checklist{truths, artifacts, key_links}the default-FAIL evaluator grades against at VERIFY. No must_haves ⇒ the evaluator has only the acceptance line.requirements— requirement IDs this task covers (traceability), when the phase has them.
- Checkpoints. Where a human must verify/decide, add
{key,title,after,how}; make downstream tasks depend oncp:<key>so the wave blocks until the human closes it. - Self-check (goal-backward, GSD plan-checker's 7 dimensions). Before applying, verify: requirement coverage · task completeness (acceptance+verify present) · dependencies acyclic · artifacts wired together (not isolated) · scope within context budget · acceptance is user-observable · honors the user's frozen decisions. Fix gaps — don't apply a plan that won't reach the goal.
- Apply. Emit the plan as JSON and pipe it to the materializer:
cat <<'PLAN' | cmpl plan-apply…PLAN. It creates the epic + tasks + deps + checkpoints + abd swarm(native waves). Then showbd readyandbd swarm status.
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 · 41 lines · 96 tokens per session scan A 865b48bdae39
completely:plan is a skill published in the GitHub repository 23ag1/completely (5 stars, last pushed 2mo ago), licensed MIT. It adds 96 tokens to every session and 813 once invoked, about $0.0005 per session on Opus 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-31.
Other skills, from other repositories
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
openai-whisper-api
Transcribe audio via OpenAI Audio Transcriptions API (Whisper).
perf-code-paths
Use when mapping code paths, entrypoints, and likely hot files before profiling.
compare-harnesses
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.
repo-genome
7-section readiness scorecard for a LOCAL repo. Reports repo type + agent topology + MCP risk + test confidence + release readiness + recommended harness plan + scorecard. Exit 0 ready, 1 needs-work, 2 blocked. --json for the 6-field scorecard, --bundle for the ADR-031 schema-1 envelope.