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 agentmods add skills/shinpr/linear-prism/decomposition-guidenpx skills add shinpr/linear-prism --skill decomposition-guidegit clone --depth 1 https://github.com/shinpr/linear-prismWrote 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/shinpr/linear-prism/decomposition-guide)<a href="https://agentmods.dev/skills/shinpr/linear-prism/decomposition-guide"><img src="https://agentmods.dev/badge/skills/shinpr/linear-prism/decomposition-guide.svg" alt="Measured on agentmods" 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 | $0.00032 | $0.01035 |
| Opus 5 | $0.00016 | $0.00517 |
| Sonnet 5 | $0.00006 | $0.00207 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
decomposition-guide 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 4d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Defines criteria for independently verifiable implementation tasks with explicit responsibility scopes and real dependency edges. Used by the task-decomposer-linear agent during decompose and revise modes.
Task Decomposition Principles
Value-Unit Definition
A value-unit task delivers one coherent, verifiable outcome:
- User-facing value: A behavior change observable by end users or API consumers.
- System-facing value: An infrastructure change that enables subsequent user-facing work (shared contract, migration, test harness).
Each value-unit task satisfies all of the following:
- Produces a deployable or mergeable increment when completed.
- Has an independently observable completion condition.
- Depends only on deliverables that must exist before its outcome can be completed or verified.
Task Types
| Type | When to use | Example |
|---|---|---|
value_unit |
Delivers one coherent user-facing or system-facing value | "User can submit review from Word add-in" |
shared_prerequisite |
Two or more later tasks depend on the same missing foundation at a shared boundary | "Define shared API contract for review requests" |
Shared Prerequisite Extraction
Create a shared_prerequisite task only when ALL conditions hold:
- Two or more later value-unit tasks depend on the same missing piece.
- The piece changes a shared boundary (contract, interface, infrastructure path, test harness).
- The boundary must stabilize before the earliest dependent value unit can complete and verify its outcome.
Limit the prerequisite to what the earliest executable value-unit task needs. When the split is ambiguous, keep the work inside that value-unit task and record the uncertainty in dependency_notes.
Slicing Strategy
Vertical Slice (Feature-by-Feature)
Use by default when each task can deliver and verify one outcome across its affected layers.
Horizontal Slice (Layer-by-Layer)
Use only when a shared foundation is an independently verifiable deliverable that must stabilize before every dependent value unit can execute or verify its outcome.
What ships with it
1 file 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.
- 4d ago First seen · 108 lines · 32 tokens per session scan A beb971b343b9
decomposition-guide is a skill published in the GitHub repository shinpr/linear-prism (7 stars, last pushed 16d ago), licensed MIT. It adds 32 tokens to every session and 1,035 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
linear-cli
Manage Linear issues from the command line using the linear cli. This skill allows automating linear management.
Release
This skill should be used when the user asks to "make a release", "create a release", "cut a release", "release a new version", "publish a release", or mentions preparing for release. Provides comprehensive workflow for reviewing changes, updating changelog, determining semver bump, and publishing.
release-core-test
Invoke when dev-testing a Cyrus change that spans CYPACK (edgeworker + CLI) and CYHOST (Vercel-hosted GUI) and the hosted GUI needs to point at an unreleased cyrus-core from this repo. Publishes cyrus-core (and claude-runner if needed) as a -test.N prerelease under the npm test dist-tag so CYHOST can install it via…
cyrus-setup-claude-auth
Configure Claude Code authentication for Cyrus — API key, OAuth token, or third-party provider.
f1-test-drive
Orchestrate F1 test drives to validate the Cyrus agent system end-to-end across issue-tracker, EdgeWorker, and activity rendering.
verify-and-ship
Run all quality checks (tests, lint, typecheck), fix failures, update the changelog, commit, push, and create/update the pull request or merge request.