Borrowing it
Nothing to install: this file belongs to AlexisBalayre/claude-code-power-config. 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/AlexisBalayre/claude-code-power-config/main/.claude/skills/to-epic/SKILL.mdgit clone --depth 1 https://github.com/AlexisBalayre/claude-code-power-configWrote 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/alexisbalayre/claude-code-power-config/to-epic)<a href="https://agentmods.dev/skills/alexisbalayre/claude-code-power-config/to-epic"><img src="https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/to-epic/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/alexisbalayre/claude-code-power-config/to-epic"><img src="https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/to-epic.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.00036 | $0.01099 |
| Opus 5.5 | $0.00014 | $0.00440 |
| Sonnet 5.5 | $0.00007 | $0.00220 |
| Haiku 4.5 | $0.00004 | $0.00110 |
Grade A, and why
to-epic 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 2mo 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To Epic
Take what you already know from the current conversation and codebase exploration, produce an Epic, and file it as an issue. Do NOT interview the user from scratch; synthesize what's already on the table.
Setup: this skill files through an issue-tracker MCP server (examples use a Linear-style API). Read your tracker IDs from
.env(see.env.example) and enable the server in.claude/settings.local.json. Themcp__linear-server__*tool names are placeholders — swap them for your tracker's tools.
Tracker metadata
Read these from .env (never hardcode real account IDs in the repo):
- Assignee:
${TRACKER_ASSIGNEE_ID} - Team:
${TRACKER_TEAM_ID} - Project:
${TRACKER_PROJECT_ID} - Label:
${TRACKER_EPIC_LABEL_ID}(Epic) — always apply
Process
1. Ground truth
If the relevant area has not been explored yet, do so now. Anchor the Epic in:
docs/glossary.mdanddocs/conventions/core.mdfor vocabulary. The Epic body MUST use these terms (e.g.,Organization,Session,Message); flag and resolve any drift before drafting.docs/reference/for current service boundaries and wiring.docs/explanation/for the rationale of the surrounding subsystem.docs/adr/for hard-to-reverse decisions already locked in. The Epic must not silently re-litigate an existing ADR; if it does, call it out explicitly and decide whether to open a new ADR that supersedes it..claude/rules/*.mdfor the area you'll touch.
For why/how questions across services, delegate to the architecture-explainer subagent.
2. Module sketch
Sketch the major modules to build or modify. Run the /codebase-design skill for the vocabulary, and actively look for deep modules: a simple, testable interface that hides complex implementation and rarely changes. Shallow modules with thin interfaces over large surface area are a smell; surface them and consolidate.
Confirm with the user before drafting:
- Does this module breakdown match your expectations?
- Which modules need test coverage first?
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.
- 2mo ago First seen · 106 lines · 36 tokens per session scan A 08095d38a97f
to-epic is a skill published in the GitHub repository AlexisBalayre/claude-code-power-config (2 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 1,099 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
operator-scorecard
Three recap modes - default synthesizes agent health, community growth, and economic activity into a was-it-worth-it verdict; ops recaps what shipped and failed; push ranks push impact.
github-monitor
Watch your GitHub repos across four views - a combined urgency monitor (stale PRs, new issues, releases), a new-issue triage queue, a release upgrade digest, or your own opened-PR tracker.
heartbeat
Ambient fleet-health check that surfaces anything worth attention (default), or an on-demand priority brief - the 3 things to focus on, why now, and what moved (var=brief).
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
idea-pipeline
Execution-gap audit - cross-references the startup idea backlog against shipped skills, prototypes, and cross-repo PRs, surfacing the top 3 ideas to build next by narrative and operator fit.
strategy-builder
Draft STRATEGY.md from a goal - read the operator's brief (goal, repo, links) plus the repo README and memory, then write a tight north-star/priorities/audience/constraints strategy.