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 Tarekkharsa/agentstack --skill breakdowngit clone --depth 1 https://github.com/Tarekkharsa/agentstackWrote 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/tarekkharsa/agentstack/breakdown)<a href="https://agentmods.dev/skills/tarekkharsa/agentstack/breakdown"><img src="https://agentmods.dev/badge/skills/tarekkharsa/agentstack/breakdown/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/tarekkharsa/agentstack/breakdown"><img src="https://agentmods.dev/badge/skills/tarekkharsa/agentstack/breakdown.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.00025 | $0.00367 |
| Opus 5.5 | $0.00010 | $0.00147 |
| Sonnet 5.5 | $0.00005 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
linear_breakdown 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
Linear Breakdown
Unofficial, agentstack-authored. Not affiliated with or endorsed by Linear.
Use this skill when a Linear issue is too big to ship in one pass and needs to be split into smaller tickets a team can pick up independently.
Workflow
- Read the parent issue end to end. Pull out the user-facing outcome, the acceptance criteria, and any constraints (deadlines, owners, affected areas).
- Decompose by shippable slice, not by layer. Each child ticket should be something that can land and be verified on its own — avoid "backend ticket" + "frontend ticket" pairs that only make sense merged.
- For every child ticket, write:
- a title in imperative voice ("Add X", "Migrate Y"),
- a one-line outcome and explicit acceptance criteria,
- a rough size (S / M / L) — split anything that reads as L,
- dependencies on sibling tickets, if any.
- Order the tickets so the first one delivers value or unblocks the rest. Flag the critical path.
- Link every child back to the parent and keep the parent as the tracking issue.
Conventions
- Prefer 3–7 children. More than that usually means the slices are too thin.
- Each child should be mergeable within roughly a day of focused work.
- Never invent acceptance criteria the parent does not support — ask instead.
When using the Linear MCP, create the parent's sub-issues rather than detached issues, and set the team/project to match the parent so the breakdown stays grouped.
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 · 38 lines · 25 tokens per session scan A 2a247a0d111f
linear_breakdown is a skill published in the GitHub repository Tarekkharsa/agentstack (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 367 once invoked, about $0.0001 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
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
session-handoff
Close out a work session on Arthur MCP by updating docs/HANDOFF.md and docs/ROADMAP.md and reporting which validation commands were run. Use at the end of a task, before telling the user work is complete.
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…