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 dissectgit 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/dissect)<a href="https://agentmods.dev/skills/afaraha8403/balakit/dissect"><img src="https://agentmods.dev/badge/skills/afaraha8403/balakit/dissect/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/dissect"><img src="https://agentmods.dev/badge/skills/afaraha8403/balakit/dissect.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.00176 | $0.06074 |
| Opus 5.5 | $0.00070 | $0.02430 |
| Sonnet 5.5 | $0.00035 | $0.01215 |
| Haiku 4.5 | $0.00018 | $0.00607 |
Grade A, and why
dissect 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 — 539 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dissect
Leading words: dissect, ground truth, entity-level, minimal-build, red-team, evidence-backed, stub detection, naming audit, fold test, phase separation, patch in place, circuit, autopilot, plain question.
Systematically interrogate and optimize an existing service, written plan, or system. The goal is not to rubber-stamp the current design — it is to arrive at the minimal-build plan that correctly meets the requirements, by challenging every assumption with live evidence and an adversarial review panel.
Trigger: /dissect [--circuit|--autopilot] <target> where <target> is a
service name, plan file path, codebase area, or free-form description. If
omitted, ask. Pace flags are optional; default is interactive (stop at every
checkpoint).
dissect is the backward-looking counterpart to deep-deliberation. They share
DNA — parallel read-only sub-agents, devil's-advocate red-teaming, human
checkpoints, evidence over intent, and the same --circuit / --autopilot
grammar — but point in opposite directions: deliberation designs what to build;
dissect audits what already exists.
User Input
$ARGUMENTS
Parse a pace flag from arguments before treating the rest as <target>:
--circuit, --autopilot, --auto (alias of --autopilot). Strip the flag
from the target string. If both circuit and autopilot appear, autopilot wins.
Pace modes (optional)
Default is interactive: stop and wait at every checkpoint.
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, "just audit this", or a
desire to move fast. Mid-run, the same phrases switch mode from the current
checkpoint. stop circuit / stop autopilot drops back to interactive.
| Mode | Intermediate checkpoints (1–2) | Final checkpoint (3) |
|---|---|---|
interactive |
Stop and wait | Stop and wait. Do not proceed until they ask |
--circuit |
Auto-accept the recommended choice; log and continue | Stop. Ask whether to go ahead with the final recommendation |
--autopilot |
Auto-accept; log and continue | Auto-accept. Treat the recommendation as the way to proceed |
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.
- 1mo ago Changed · +129 lines · +33 tokens per session 70bbb1473136
- 1mo ago Changed · +14 lines d53b235870e1
- 1mo ago First seen · 396 lines · 143 tokens per session scan A 9801ce453871
dissect is a skill published in the GitHub repository afaraha8403/balakit (1 stars, last pushed 1mo ago), licensed MIT. It adds 176 tokens to every session and 6,074 once invoked, about $0.0007 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-08-31.
Other skills, from other repositories
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.
refactoring-guru
Apply Refactoring.Guru-inspired rules when diagnosing code smells, choosing refactoring techniques, and stopping cleanup before uncontrolled redesign.
refactoring
Apply Martin Fowler-inspired refactoring rules when improving existing code structure while preserving observable behavior.
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
atmos-introspection
Introspection & Querying: describe/list commands, config filtering, workspace introspection, dependency graphs, YQ integration, --help= scoped CLI help.
atmos-schemas
JSON Schema for Atmos: stack-manifest and atmos.yaml config schemas, IDE auto-completion, validate stacks/schema/config, SchemaStore integration.