Borrowing it
Nothing to install: this file belongs to TheSmokeDev/taskchad-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/TheSmokeDev/taskchad-os/master/.claude/skills/vertical-slice-audit/SKILL.mdgit clone --depth 1 https://github.com/TheSmokeDev/taskchad-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/thesmokedev/taskchad-os/vertical-slice-audit)<a href="https://agentmods.dev/skills/thesmokedev/taskchad-os/vertical-slice-audit"><img src="https://agentmods.dev/badge/skills/thesmokedev/taskchad-os/vertical-slice-audit/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/thesmokedev/taskchad-os/vertical-slice-audit"><img src="https://agentmods.dev/badge/skills/thesmokedev/taskchad-os/vertical-slice-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00105 | $0.01823 |
| Opus 5 | $0.00053 | $0.00911 |
| Sonnet 5 | $0.00021 | $0.00365 |
| Haiku 4.5 | $0.00011 | $0.00182 |
Grade A, and why
vertical-slice-audit 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 5d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vertical Slice Audit — Score a Feature, Produce a Migration Plan
You are auditing a single feature/folder for adherence to Vertical Slice Architecture (VSA). VSA is the codebase-level optimization that lets a coding agent load one slice end-to-end and ship — instead of chasing cross-folder context across layered architecture.
Target path: $1 (the feature folder to audit). If $1 is empty, ask the user which feature to audit before proceeding.
What you will do
- Read the target folder at
$1 - Walk the 10-row checklist below, scoring each row
- Classify the slice based on the total score
- If the slice fails (score < 9/10), produce a step-by-step migration plan
- Report results to the user
The 10-Row Checklist
For the feature at $1, score each row PASS or FAIL:
| # | Check | PASS | FAIL |
|---|---|---|---|
| 1 | Feature has its own folder | All its code lives under one top-level folder | Code is spread across controllers/, services/, models/, repositories/ |
| 2 | Models are local to the feature | <feature>/models.{py,ts} exists |
Models in a top-level shared folder |
| 3 | Schemas are local to the feature | <feature>/schemas.{py,ts} exists |
Schemas in a top-level shared folder |
| 4 | Routes are local to the feature | <feature>/routes.{py,ts} (or routes registered from here) |
Routes in a top-level shared folder |
| 5 | Business logic is local | <feature>/service.{py,ts} contains the substance |
Logic spread across helpers, utils, lib |
| 6 | Errors are local | <feature>/errors.{py,ts} defines feature-specific exceptions |
All errors are generic shared exceptions |
| 7 | Tests are colocated | <feature>/tests/ exists next to the source |
Tests in a top-level tests/ folder |
| 8 | Public API is explicit | Feature has an index.{ts} or __init__.py that controls exports |
Anything can be imported from anywhere |
| 9 | Internal helpers stay internal | Private functions are not exposed via the public API | Everything is exported |
| 10 | Cross-feature dependencies are minimal | Feature imports from <3 other features (excluding shared utils) | Feature imports from many other features |
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.
- 5d ago First seen · 167 lines · 105 tokens per session scan A 3ad2afd76b0c
vertical-slice-audit is a skill published in the GitHub repository TheSmokeDev/taskchad-os (23 stars, last pushed 2d ago), licensed MIT. It adds 105 tokens to every session and 1,823 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
insights
Use when the user types /weekly or /monthly, asks for a weekly or monthly journal review or retrospective, asks 'how was my week' or 'how was my month', or wants trends, anomalies, or patterns across recent journal entries. Also fires when regenerating an insight report for a past week or month. NOT for writing…
patterns
Use when the user says /patterns or mentions the Instinct Engine, says "I keep noticing" or "this keeps coming up", after a weekly review, when a pattern is hardening, or at session end after repeated corrections, 5+ tool-call friction on a routine task, dead-end backtracking, or an undocumented discovery. Also as a…
evolve
Use when many related hardened instincts (high-confidence feedback/discovery memories) have piled up in one domain, when the user runs /evolve or asks to promote, cluster, graduate, or consolidate accumulated instincts into a Command, Skill, or Agent, or when files in Instinct Proposals need review. Part of the…
memory-to-skill
Turn workflows from your MemSearch memory into reusable skills. Use when the user asks to make/create/extract/distill a skill from what they just did or from past work, review skill candidates, install a distilled skill, or 'turn this into a skill'. Manages MemSearch procedural-memory candidates under…
pr-body
A tool that reviews all commits on the current branch and creates or updates a pull request title and description. A pull request is a proposed code change submitted for review.
quality-gate
Orchestrates the QUALITY pipeline stage for egregore work items, running code review, unbloat, and test updates. Use when running quality checks before a PR.