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/phobologic/claude_code_helpers/epic-treenpx skills add phobologic/claude_code_helpers --skill epic-treegit clone --depth 1 https://github.com/phobologic/claude_code_helpersWhat 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.00039 | $0.00298 |
| Opus 5 | $0.00019 | $0.00149 |
| Sonnet 5 | $0.00008 | $0.00060 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
epic-tree 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 2d 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
Run tk epic-tree with the arguments from the user's command and display the output verbatim.
Parse the command arguments directly from the user's message:
- Any ticket IDs (e.g.
pbp-c0ll,abc-1234) are positional arguments --allflag shows closed sub-epics (omit it if not specified)
Examples:
/epic-tree→tk epic-tree/epic-tree pbp-c0ll→tk epic-tree pbp-c0ll/epic-tree pbp-c0ll --all→tk epic-tree pbp-c0ll --all/epic-tree abc-1 abc-2→tk epic-tree abc-1 abc-2
Run the command with the Bash tool, then print the full command output verbatim as your text response — inside a fenced code block so it renders as-is. The Bash tool result is often collapsed in the UI (e.g. "+N lines, ctrl+o to expand"), so you must reproduce it in your own message. Do not summarize, truncate, reformat, or add commentary.
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.
- 2d ago First seen · 21 lines · 39 tokens per session scan A dfe04555c20c
epic-tree is a skill published in the GitHub repository phobologic/claude_code_helpers (5 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 298 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
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
teamharness-task-delegation
Use when a Leader turns ready Quick Task or Project Work state into Worker task instructions, sends assignment messages, checks submitted results, and defines completion/blocker report contracts. Do not use to create projects, create rooms, or execute Worker tasks.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…