A repository-reuse workflow that searches the user's GitHub projects for existing code before new implementation begins. It records which source files were reused or why no match was used.

Use it when adding features, APIs, authentication, or interface code, or when looking for how a similar problem was solved in an existing project.

It reduces duplicate work and avoids guessing when a tested solution may already exist in one of the user's repositories.

spokes — Skill for Claude Code and Codex by Dente22

Install

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.

Any agent

npx skills add Dente22/Spokes --skill skill

Clone the repo

git clone --depth 1 https://github.com/Dente22/Spokes

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/dente22/spokes/skill/github.svg)](https://agentmods.dev/skills/dente22/spokes/skill)

Your own site

<a href="https://agentmods.dev/skills/dente22/spokes/skill"><img src="https://agentmods.dev/badge/skills/dente22/spokes/skill/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/dente22/spokes/skill"><img src="https://agentmods.dev/badge/skills/dente22/spokes/skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 685 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00072	$0.00685
Opus 5.5	$0.00029	$0.00274
Sonnet 5.5	$0.00014	$0.00137
Haiku 4.5	$0.00007	$0.00068

Measured 1mo ago against content hash 32ef92122b34, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spokes 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.

skill/SKILL.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spokes — reuse your repos first

Spokes is a local MCP memory of the user's GitHub repositories. Treat it as a cheat sheet: if a working piece already exists in their repos, take/adapt it into the active project instead of inventing from scratch.

Always-on workflow

For every non-trivial implementation task:

Call start_task with a short description of the user request. Keep the returned task_id.
Call search_repos with the task keywords and task_id.
If matches exist:
- get_repo_card on the best candidates
- list_tree / search_in_repo / get_file to pull only the needed pieces
- Adapt into the active project
- Call log_step for every action so Reuse flow shows the complete chain.
- For reuse, always include:
  - repo_full_name + source path
  - source_start_line / source_end_line when known
  - target_path in the active project
  - target_start_line / target_end_line when known
  - detail: what changed and why
If no useful match: call log_step with action skip_no_match, then implement normally. Do not force bad reuse.

Rules

Prefer Spokes-backed reuse over guessing APIs/patterns the user already owns.
Keep context small: fetch files/ranges, not whole repositories.
Pass task_id into tools whenever possible so the web journal stays accurate.
Do not combine several actions into one log_step. Ten actions must be ten steps in Reuse flow.
Never print the user's GitHub access token.
If tools say GitHub is not connected, tell the user to open http://127.0.0.1:3847, click Connect GitHub, and approve Spokes in their browser.

Tool map

Need	Tool
Open audit task	`start_task`
Find candidate repos	`search_repos`
Inspect brief memory	`get_repo_card` / `list_repos`
Browse files	`list_tree`
Read code	`get_file`
Search inside one repo	`search_in_repo`
Record reuse decision	`log_step`
Read journal	`get_task_journal`

Read the full file on GitHub · 66 lines

Changes

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 · 66 lines · 72 tokens per session scan A 32ef92122b34

Subscribe to this mod's changes

spokes is a skill published in the GitHub repository Dente22/Spokes (1 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 685 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.

Building agents Productivity ai-agent code-reuse cursor developer-tools github mcp

adhd-output-style

This skill should be used when the user asks for "ADHD output", "fewer output tokens", "short numbered steps", "limited working memory formatting", or explicitly invokes "adhd-output-style".

fcakyon/claude-codex-settings · 46 tokens

peon-ping-toggle

Toggle peon-ping sound notifications on/off. Use when user wants to mute, unmute, pause, or resume peon sounds during a Claude Code session. Also handles config changes like volume, pack rotation, categories — any peon-ping setting.

PeonPing/peon-ping · 58 tokens

peon-ping-log

Log exercise reps for the Peon Trainer. Use when user says they did pushups, squats, or wants to log reps. Examples - "/peon-ping-log 25 pushups", "/peon-ping-log 30 squats", "log 50 pushups".

PeonPing/peon-ping · 64 tokens

polar-billing

This skill should be used when working on Polar billing system, Stripe integration, subscription lifecycle, checkout flows, or benefit provisioning.

fcakyon/claude-codex-settings · 29 tokens

writing-livekit-scenarios

Creates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them. Use when the user asks "what should I test", "generate simulation scenarios", "write scenarios for my agent", "add a scenario for X", "organize my scenario files", "my simulations are flaky", "the scenario hits my…

fcakyon/claude-codex-settings · 178 tokens

durable-objects

Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.

fcakyon/claude-codex-settings · 22 tokens