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 adilkalam/orca --skill precision-disciplinegit clone --depth 1 https://github.com/adilkalam/orcaWrote 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/adilkalam/orca/precision-discipline)<a href="https://agentmods.dev/skills/adilkalam/orca/precision-discipline"><img src="https://agentmods.dev/badge/skills/adilkalam/orca/precision-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/adilkalam/orca/precision-discipline"><img src="https://agentmods.dev/badge/skills/adilkalam/orca/precision-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.00070 | $0.01743 |
| Opus 5.5 | $0.00028 | $0.00697 |
| Sonnet 5.5 | $0.00014 | $0.00349 |
| Haiku 4.5 | $0.00007 | $0.00174 |
Grade A, and why
precision-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 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Precision Discipline
RULE: Every derived value cites its source. Every step produces its artifact. Every output gets measured.
When to Apply
Apply when a command or workflow flag activates precision mode:
/design --stl(STL geometry replication)- Any workflow where the output is measurable and the tolerance is defined
Do NOT apply to creative exploration, brainstorming, or research. Those use different constraint patterns.
Escape Hatch Detection
After EACH step in a precision workflow, answer these 4 questions before proceeding:
- Artifact or narrative? Did I produce the mandatory artifact for this step (table, comparison, tool output), or did I write prose ABOUT what I found?
- Sourced or summarized? Does every derived value cite a specific source (tool output field, coordinate pair, file:line), or did I use a summary phrase ("from the analysis", "based on measurements")?
- Done or moving on? Am I declaring this step complete because the artifact is complete, or because I want to get to the next step?
- Reproducible? If someone re-ran my exact tool calls with the same parameters, would they get the same values I'm reporting?
If ANY answer exposes an escape hatch: STOP. Go back. Produce the actual artifact.
Do not narrate the self-check. Do not write "I checked and all 4 passed." Either the artifact exists or it doesn't.
Constraint Chain Integration
Use cognition-mcp checkpoint calls to track precision constraints. Same cognition-mcp mechanism, with execution-specific constraint types.
Constraint Types
| Type | Meaning | Resolves when |
|---|---|---|
| EVIDENCE | Must produce this artifact before proceeding | Artifact exists in output |
| VERIFY | Must measure output against reference | Comparison tool call completed with results shown |
| FORBIDDEN | Cannot do this at all | Never resolves -- permanent constraint |
| UNKNOWN | Gap that cannot be filled from available data | User provides the value, or explicitly accepted as unknown |
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 · 175 lines · 70 tokens per session scan A 49521d18b623
precision-discipline is a skill published in the GitHub repository adilkalam/orca (2 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 1,743 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…