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 kryptobaseddev/cleo --skill ct-epic-architectgit clone --depth 1 https://github.com/kryptobaseddev/cleoWrote 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/kryptobaseddev/cleo/ct-epic-architect)<a href="https://agentmods.dev/skills/kryptobaseddev/cleo/ct-epic-architect"><img src="https://agentmods.dev/badge/skills/kryptobaseddev/cleo/ct-epic-architect/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/kryptobaseddev/cleo/ct-epic-architect"><img src="https://agentmods.dev/badge/skills/kryptobaseddev/cleo/ct-epic-architect.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.00077 | $0.02924 |
| Opus 5.5 | $0.00031 | $0.01170 |
| Sonnet 5.5 | $0.00015 | $0.00585 |
| Haiku 4.5 | $0.00008 | $0.00292 |
Grade A, and why
ct-epic-architect 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 20d 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 — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Epic Architect Context Injection
Protocol: @src/protocols/decomposition.md Type: Context Injection (cleo-subagent) Version: 3.0.0
Purpose
Context injection for epic planning and task decomposition tasks spawned via cleo-subagent. Provides domain expertise for breaking down large initiatives into atomic, executable tasks.
Capabilities
- Epic Creation - Parent epic with full metadata and file attachments
- Task Decomposition - Atomic tasks with acceptance criteria
- Dependency Analysis - Wave-based parallel execution planning
- Research Linking - Connect research outputs to tasks
- HITL Clarification - Ask when requirements are ambiguous
Task System Integration
@skills/_shared/task-system-integration.md
Execution Sequence
- Read task:
cleo show {{TASK_ID}} - Start task:
cleo start {{TASK_ID}}. Ifcleo startfails withE_SESSION_UNBOUND(spawned workers and subagents are already bound), runcleo session start --scope global --name "<name>"orcleo session resume <id>first. - Check existing work:
cleo find "keyword",cleo list --type epic - Create epic and child tasks
- Attach files and link research
- Start session:
cleo session start --scope epic:{{EPIC_ID}} --name "<what you are doing>" - Complete task:
cleo complete {{TASK_ID}}
Requirements Analysis
MUST check for related work BEFORE creating:
cleo find "auth" --status pending # Related tasks
cleo list --type epic --status pending # Existing epics
cleo phase show # Current phase
cleo list --tree --parent T001 # Hierarchy view
Epic Structure
Epic (type: epic, size: large)
├── Task 1 (no deps) [Wave 0]
├── Task 2 (depends: T1) [Wave 1]
├── Task 3 (depends: T1) [Wave 1] ← Parallel
├── Task 4 (depends: T2,T3) [Wave 2] ← Convergence
└── Task 5 (depends: T4) [Wave 3]
Tier Sizing & Scope (canonical source: ADR-073 §1.1)
What ships with it
10 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.
- references/bug-epic-example.md 5.3 KB
- references/commands.md 5.5 KB
- references/feature-epic-example.md 6.4 KB
- references/migration-epic-example.md 8.2 KB
- references/output-format.md 2.6 KB
- references/patterns.md 9.0 KB
- references/refactor-epic-example.md 14 KB
- references/research-epic-example.md 6.6 KB
- references/shell-escaping.md 2.1 KB
- references/skill-aware-execution.md 5.5 KB
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.
- 20d ago Changed 1dd6debaff52
- 21d ago Changed · +3 lines 64ce783387a7
- 22d ago Changed · +4 lines 0c0fd3f57fdc
- 1mo ago First seen · 348 lines · 77 tokens per session scan A acf278258170
ct-epic-architect is a skill published in the GitHub repository kryptobaseddev/cleo (159 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 2,924 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-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.