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 kit-workflowsgit 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/kit-workflows)<a href="https://agentmods.dev/skills/afaraha8403/balakit/kit-workflows"><img src="https://agentmods.dev/badge/skills/afaraha8403/balakit/kit-workflows/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/kit-workflows"><img src="https://agentmods.dev/badge/skills/afaraha8403/balakit/kit-workflows.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.00080 | $0.00423 |
| Opus 5.5 | $0.00032 | $0.00169 |
| Sonnet 5.5 | $0.00016 | $0.00085 |
| Haiku 4.5 | $0.00008 | $0.00042 |
Grade A, and why
kit-workflows 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.
What it actually says
Kit workflows
Leading words: match a playbook, copy steps, skip with reason, prove on the real path.
Not a sticky mode. Match the task to one playbook. Copy that file's steps
into the todo list verbatim. Skipped steps stay with skip: / n/a:.
| Playbook | When |
|---|---|
| playbooks/bug-fix.md | A defect: reproduce, root-cause, fix with evidence |
| playbooks/feature.md | New or changed behavior from a named data shape |
| playbooks/refactor.md | Behavior-preserving reshape |
If none match, stop and use unmatched-workflow.
Reply contract
First line: Playbook: bug-fix, Playbook: feature, or Playbook: refactor.
Then what was verified, and any skip: lines.
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 First seen · 43 lines · 80 tokens per session scan A e4e7e98d294d
kit-workflows is a skill published in the GitHub repository afaraha8403/balakit (1 stars, last pushed 29d ago), licensed MIT. It adds 80 tokens to every session and 423 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-11.
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.
browser-trace
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page…
ontoly-software-graph
Use Ontoly's deterministic Software Graph and MCP capabilities for repository architecture, request tracing, dependency analysis, configuration lookup, and impact analysis before falling back to source search.
designing-data-intensive-applications
Apply Martin Kleppmann-inspired data-system rules when designing reliability, scalability, consistency, replication, transactions, streams, or schema evolution.