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-issues/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-issues)<a href="https://agentmods.dev/skills/alexisbalayre/claude-code-power-config/to-issues"><img src="https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/to-issues/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-issues"><img src="https://agentmods.dev/badge/skills/alexisbalayre/claude-code-power-config/to-issues.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.00042 | $0.01365 |
| Opus 5.5 | $0.00017 | $0.00546 |
| Sonnet 5.5 | $0.00008 | $0.00273 |
| Haiku 4.5 | $0.00004 | $0.00136 |
Grade A, and why
to-issues 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To Issues
Break a plan into small, end-to-end vertical slices. Each slice crosses every layer the feature touches (schema, service, transport, UI, tests) for one narrow behavior, rather than covering all of one layer for many behaviors.
Setup: this skill files tickets through an issue-tracker MCP server (the examples use a Linear-style API). Fill in your own IDs below and enable the server in
.claude/settings.local.json. The tool names (mcp__linear-server__*) 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}
Process
1. Source
If the user passes an issue ID or URL, fetch it via mcp__linear-server__get_issue and read the full body + comments. Otherwise work from the current conversation context.
2. Ground truth
Issue titles and bodies MUST use this repo's vocabulary. Before slicing:
- Skim
docs/glossary.mdanddocs/conventions/core.mdfor canonical terms (Organization,Session,Participant,Message, etc.). - Check
docs/adr/for hard-to-reverse decisions in the area. If any proposed slice would silently re-litigate an ADR, flag it to the user before drafting; do not bury the contradiction inside an issue body. - Skim the relevant
docs/explanation/<topic>.mdfor current rationale.
For why/how questions across services, delegate to the architecture-explainer subagent.
3. Slice
Break the plan into vertical slices. A wide refactor is the exception to the vertical-slice rule — slice it by expand–contract instead (see Wide refactors below). For each slice:
- Title: imperative, action-oriented, in repo vocabulary.
- Type: HITL (needs human input: architectural decision, design review, manual verification) or AFK (can be implemented and merged unattended). Prefer AFK; treat HITL as a flag that the slice still has an unresolved question.
- Blocked by: which other slices must complete first.
- User stories covered: which stories from the parent Epic (if any).
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 · 112 lines · 42 tokens per session scan A f7f147e1285a
to-issues is a skill published in the GitHub repository AlexisBalayre/claude-code-power-config (2 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 1,365 once invoked, about $0.0002 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.