Borrowing it
Nothing to install: this file belongs to walm00/business-context-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/walm00/business-context-os/main/.claude/skills/core-discipline/SKILL.mdgit clone --depth 1 https://github.com/walm00/business-context-osWrote 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/walm00/business-context-os/core-discipline)<a href="https://agentmods.dev/skills/walm00/business-context-os/core-discipline"><img src="https://agentmods.dev/badge/skills/walm00/business-context-os/core-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/walm00/business-context-os/core-discipline"><img src="https://agentmods.dev/badge/skills/walm00/business-context-os/core-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.00027 | $0.01123 |
| Opus 5 | $0.00014 | $0.00562 |
| Sonnet 5 | $0.00005 | $0.00225 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
core-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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core Discipline: The 1% Rule
Inspired by Superpowers framework
The Fundamental Rule
If there's a reasonable chance a skill applies to what you're doing, CHECK it. Match the overhead to the task.
- Small change (update one data point, fix a typo) → just do it, no ceremony
- Medium change (add a new data point, consolidate two docs) → check if context-audit or context-ingest applies
- Significant change (restructure a cluster, create new skills) → use clear-planner, run the full workflow
The point is not to invoke every skill every time. The point is to not miss the ones that matter.
Purpose
This skill IS:
- A bootstrap discipline enforcing proactive skill discovery before every action
- An always-active overlay that applies throughout any session
- The entry point that ensures other skills are found and invoked when relevant
This skill IS NOT:
- A substitute for the specific skills it discovers (it finds them, they do the work)
- A workflow orchestrator (use
clear-plannerfor that) - Something you invoke explicitly -- it is always active
Default Behavior
Keep it simple. Match response to task.
| Task Type | Action |
|---|---|
| Questions, commands | Respond directly |
| Single-file fixes | Just do it |
| Small changes (1-3 files) | Think briefly, execute |
When in doubt: Ask the user — via AskUserQuestion, not prose (see "Decision-point UX" below).
Decision-point UX (cross-cutting)
Every decision point in every BCOS interaction uses AskUserQuestion. Not prose "should I do X?" questions. Not lists of options typed as text. Structured choice, clickable menu, dashboard-aware session state.
Applies everywhere: onboarding, ingest, audit, tune, migrate, dispatcher output, update confirmations, archival decisions, every skill that offers the user choices.
What ships with it
2 files 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.
- 10d ago First seen · 116 lines · 27 tokens per session scan A ab3b9e071604
core-discipline is a skill published in the GitHub repository walm00/business-context-os (21 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 1,123 once invoked, about $0.0001 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-30.
Other skills, from other repositories
wiki-ingest
Ingest supplied source material into an Obsidian vault with provenance and claim tracking: pasted text, files staged in the selected vault's inbox or .raw archive, or explicitly approved URLs. Use for a single source or bounded batch, not for saving an assistant answer. Triggers: ingest, ingest this file, ingest this…
autoresearch
Run a bounded, source-grounded research loop, draft a cited dossier, and optionally propose a separately reviewed canonical vault merge. Use when the user wants autonomous or deep research that may access the public web. Triggers: /autoresearch, autoresearch, research this topic, deep dive into, investigate, find…
canvas
Create, inspect, and update Obsidian JSON Canvas boards with text, file, link, group, and edge nodes. Use for canvas status, canvas lists, visual maps, zones, spatial layouts, adding vault notes or media to a .canvas file, and requests such as create canvas, add to canvas, or put this on the canvas.
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
wiki
Initialize, adopt, and route work for a separate Obsidian knowledge vault through the portable claude-obsidian core. Use for vault setup, scaffolding, workspace selection, cross-project configuration, or choosing the correct wiki sub-skill. Triggers: /wiki, set up wiki, scaffold vault, create knowledge base, adopt…
defuddle
Plan and, with explicit network consent, use an optional external Defuddle cleaner to extract article-like HTTPS pages as Markdown. Use for defuddle, clean this URL, strip page clutter, readable Markdown from a web page, or preparing a web source for later wiki ingestion.