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 rube-de/cc-skills --skill nextgit clone --depth 1 https://github.com/rube-de/cc-skillsWrote 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/rube-de/cc-skills/next)<a href="https://agentmods.dev/skills/rube-de/cc-skills/next"><img src="https://agentmods.dev/badge/skills/rube-de/cc-skills/next/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/rube-de/cc-skills/next"><img src="https://agentmods.dev/badge/skills/rube-de/cc-skills/next.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.00083 | $0.01740 |
| Opus 5.5 | $0.00033 | $0.00696 |
| Sonnet 5.5 | $0.00017 | $0.00348 |
| Haiku 4.5 | $0.00008 | $0.00174 |
Grade A, and why
next 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 1mo 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next: Issue Triage & Recommendation
Analyze open GitHub issues, build a dependency graph, and recommend the highest-impact issue to work on next.
Workflow
1. Fetch & Pre-process → 2. Build Dependency Graph → 3. Detect Cycles
→ 4. Rank Issues → 5. Present Recommendations → 6. Select & Assign
Step 1: Fetch and Pre-process Issues
Run the open-issues.sh script from the plugin's scripts/ directory:
# Auto-detect repository from current directory
sh "${CLAUDE_SKILL_DIR}/../../scripts/open-issues.sh"
# Or specify repository explicitly
sh "${CLAUDE_SKILL_DIR}/../../scripts/open-issues.sh" OWNER/REPO
# Include assigned issues in results
sh "${CLAUDE_SKILL_DIR}/../../scripts/open-issues.sh" --include-assigned
Validate the response:
- Check stderr for a JSON
errorobject — if present, abort with the error message (auth failures, missing tools, repo detection failures are handled by the script) - Extract and store the full JSON output as
$ISSUES_DATA
Edge case — no issues: If .total_open == 0, report "No open issues found" (if --include-assigned was used) or "No unassigned issues found (try --include-assigned to include assigned items)" (default mode) and stop.
Edge case — 100+ issues: If .total_open >= 100, warn: "Results capped at 100 issues. Consider filtering by label or milestone for a broader view."
The JSON output contains pre-computed fields for each issue:
blocked_by,blocks— parsed from issue body patterns (Blocked by:,Blocks:,Depends on:)blockers_resolved—trueif all blockers are closed (not in the open issue set)unblocked—trueif no open blockers remainage_days— days since issue creationmilestone_due_on— milestone due date (ISO 8601) ornulldependency_graph.edges—[[blocker, blocked], ...]pairs for graph analysis
Step 2: Build Dependency Graph
The script pre-computes blocked_by and blocks arrays per issue, and provides dependency_graph.edges as [[blocker, blocked], ...] pairs.
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.
- 1mo ago First seen · 155 lines · 83 tokens per session scan A 9dae9ef72f01
next is a skill published in the GitHub repository rube-de/cc-skills (10 stars, last pushed 4d ago), licensed MIT. It adds 83 tokens to every session and 1,740 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-08-31.
Other skills, from other repositories
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
opportunity-solution-tree
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a…
skeptical-triage
Reusable 3-round self-challenge + arbiter pattern for filtering false positives from findings/verdicts. Use when the cost of a false-positive gate block exceeds the cost of 4 extra LLM turns.
anti-patterns
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
cost-model
Standardized cost-estimation framework for greatcto plans. Forces explicit LLM cost, infra cost, human-supervision time, and the (defensible) human-equivalent comparison. Output format is parsable by the board's /api/cost path — must follow exactly.
done-blocked
Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.