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 Samuel0101010/wisp-orchestrator --skill builder-disciplinegit clone --depth 1 https://github.com/Samuel0101010/wisp-orchestratorWrote 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/samuel0101010/wisp-orchestrator/builder-discipline)<a href="https://agentmods.dev/skills/samuel0101010/wisp-orchestrator/builder-discipline"><img src="https://agentmods.dev/badge/skills/samuel0101010/wisp-orchestrator/builder-discipline/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/samuel0101010/wisp-orchestrator/builder-discipline"><img src="https://agentmods.dev/badge/skills/samuel0101010/wisp-orchestrator/builder-discipline.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.00035 | $0.00418 |
| Opus 5 | $0.00017 | $0.00209 |
| Sonnet 5 | $0.00007 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
builder-discipline 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 10d 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
Follow this discipline on every task. It is ordered; do not skip steps.
- Read before you write. Open the files you are about to change and the files that import them. Never edit code you have not read in this session.
- Reuse before you create. If the repo already has a helper, pattern, or component for the job, use it. New files need a reason an existing file can't satisfy.
- Smallest correct change. Implement exactly what the task asks — no extra features, no speculative abstractions, no drive-by refactors. If the task seems to require a rewrite, stop and re-read it; it usually doesn't.
- Match the codebase. Copy the surrounding style: naming, imports, error handling, comment density. Your diff should look like the original author wrote it.
- Verify before you claim. Run the task's success-criteria commands (build/test/lint) yourself before finishing. If a command fails, fix the cause — never report success with failing gates, and never weaken or delete a test to make it pass.
- Leave a trail. When you make a non-obvious choice (library, schema, trade-off), record one line about it via the shared memory protocol so downstream agents don't undo it.
If you get stuck twice on the same error, step back: re-read the error top-to-bottom, form ONE hypothesis, test it with the smallest possible command. Do not loop blind retries.
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.
- 10d ago First seen · 33 lines · 35 tokens per session scan A f14e61d9f4b4
builder-discipline is a skill published in the GitHub repository Samuel0101010/wisp-orchestrator (4 stars, last pushed 5d ago), licensed Apache-2.0. It adds 35 tokens to every session and 418 once invoked, about $0.0002 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
improve
Autonomous quality improvement loop. Scores a target against a rubric, selects the highest-leverage axis, attacks it, verifies, documents, and loops. No pre-planning between iterations — each loop re-scores from scratch.
evolve
Research-driven multi-cycle improvement director. Forms causal hypotheses about why scores are low, validates them with scout agents before attacking, dispatches axis-parallel fleet attacks, extracts transferable patterns, and runs indefinitely within a budget envelope. Accumulates a persistent belief model and…
research
Focused research investigations. Converts questions into structured findings with confidence levels and source citations. Single agent by default; with --parallel (or when the question decomposes into 3+ independent angles) it spawns scout agents whose findings are compressed into a unified brief. Does not make…
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
triage
GitHub issue and PR investigator. Pulls open issues/PRs, classifies them, searches the codebase for root cause or reviews contributed code, proposes fixes with file:line references, and optionally implements fixes. Use for investigating GitHub issues and reviewing PRs; do NOT use for general code review unrelated to…
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…