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 afaraha8403/balakit --skill inceptiongit clone --depth 1 https://github.com/afaraha8403/balakitWrote 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/afaraha8403/balakit/inception)<a href="https://agentmods.dev/skills/afaraha8403/balakit/inception"><img src="https://agentmods.dev/badge/skills/afaraha8403/balakit/inception/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/afaraha8403/balakit/inception"><img src="https://agentmods.dev/badge/skills/afaraha8403/balakit/inception.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.00119 | $0.01960 |
| Opus 5.5 | $0.00048 | $0.00784 |
| Sonnet 5.5 | $0.00024 | $0.00392 |
| Haiku 4.5 | $0.00012 | $0.00196 |
Grade A, and why
inception 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 28d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inception
Leading words: host canvas, one canvas, specialist catalog, depth bar, skip the wait not the work, circuit, autopilot.
Inception authors a plan. It does not implement — except --autopilot, which
writes the plan then runs execute in this chat.
User input
$ARGUMENTS
Parse a pace flag before treating the rest as the request:
--circuit, --autopilot, --auto (alias of --autopilot). Strip the flag
from the request text. If both circuit and autopilot appear, autopilot wins.
Pace modes (optional)
Default is interactive: ask when blocked or the choice is costly.
The user must opt in this invocation — a flag above, or an explicit phrase
(circuit, autopilot, take recommended, circuit the rest,
autopilot the rest). Do not infer from urgency. Mid-run, the same phrases
switch mode from the current checkpoint. stop circuit / stop autopilot
drops back to interactive.
| Mode | Mid-plan waits | At the plan |
|---|---|---|
interactive |
Ask. Clarify. Wait. | Write plan. Stop. Recommend execute. |
--circuit |
Auto-accept recommended. PACE_LOG. |
Write plan. Stop. Recommend execute. No extra ask. |
--autopilot |
Auto-accept. PACE_LOG. |
Write plan. Run execute (auto-pick distinct families; execute's interactive default is Current-for-all). |
This skill shares --circuit / --autopilot grammar with dissect and
deep-deliberation. The final gate differs: circuit silent-stops. Only
autopilot crosses into execute.
Skip the wait, not the work. Specialists still run when they apply. Emit a
compact PACE_LOG of every auto-accepted choice.
Cannot proceed: blocked fork, no unique plan, canvas cannot be written. Stop and ask even on autopilot.
Plan Mode vs autopilot: host Plan Mode cannot implement. Do not
SwitchMode / ExitPlanMode to run execute. Degrade to circuit.
skip: plan-mode in PACE_LOG. Tell them to accept / Build / leave Plan Mode,
then /execute.
What ships with it
3 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.
- 28d ago First seen · 185 lines · 119 tokens per session scan A 2fba081a8a08
inception is a skill published in the GitHub repository afaraha8403/balakit (1 stars, last pushed 29d ago), licensed MIT. It adds 119 tokens to every session and 1,960 once invoked, about $0.0005 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-18.
Other skills, from other repositories
designing-data-intensive-applications
Apply Martin Kleppmann-inspired data-system rules when designing reliability, scalability, consistency, replication, transactions, streams, or schema evolution.
domain-driven-design-distilled
Apply Vaughn Vernon-inspired lightweight DDD rules when using bounded contexts, subdomains, context maps, and tactical modeling without excess ceremony.
implementing-domain-driven-design
Apply Vaughn Vernon-inspired implementation DDD rules when building aggregates, domain events, repositories, application services, or context integrations.
patterns-of-enterprise-application-architecture
Apply Martin Fowler-inspired enterprise architecture rules when choosing layers, service layers, transaction scripts, domain models, repositories, mappers, or DTOs.
the-pragmatic-programmer
Apply Hunt and Thomas-inspired pragmatic programming rules when improving engineering judgment, feedback loops, DRY knowledge, orthogonality, automation, or adaptability.
working-effectively-with-legacy-code
Apply Michael Feathers-inspired legacy-code rules when changing hard-to-test code safely with characterization tests, seams, sprout methods, or wrap methods.