What is repo-followups?

A session follow-up tool that finds unfinished work, bugs, documentation gaps, and tool limitations mentioned during the conversation, then drafts issues for the appropriate repository.

Use it to turn deferred tasks and discovered problems into issues in the current repository or an upstream tool repository.

Important tasks may appear in conversation without becoming tracked work. Filing them as confirmed issues prevents them from being forgotten and can route upstream problems to the right project.

repo-followups — Skill for Claude Code and Codex by rjwalters

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 rjwalters/kicad-tools --skill repo-followups

Clone the repo

git clone --depth 1 https://github.com/rjwalters/kicad-tools

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/rjwalters/kicad-tools/repo-followups/github.svg)](https://agentmods.dev/skills/rjwalters/kicad-tools/repo-followups)

Your own site

<a href="https://agentmods.dev/skills/rjwalters/kicad-tools/repo-followups"><img src="https://agentmods.dev/badge/skills/rjwalters/kicad-tools/repo-followups/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/rjwalters/kicad-tools/repo-followups"><img src="https://agentmods.dev/badge/skills/rjwalters/kicad-tools/repo-followups.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 10,173 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.00032	$0.10173
Opus 5.5	$0.00013	$0.04069
Sonnet 5.5	$0.00006	$0.02035
Haiku 4.5	$0.00003	$0.01017

Measured 2d ago against content hash 135b4aada32b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

repo-followups 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.

.agents/skills/repo-followups/SKILL.md · 717 lines

How it starts

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

Codex form of the /repo:followups command. Other commands appear as $repo-<verb> skills. Helper scripts and .claude/ paths below are relative to the repository root and exist when the Claude Code surface is installed alongside this one.

$repo-followups — File Session Follow-Ups

Mine the current working session for follow-on work that was surfaced but not done — bugs found-but-not-fixed, deferred TODOs, documentation gaps, and limitations discovered in an upstream tool while using it — then file each as an issue in the right repo (this repo, or an upstream tool repo like Loom / Anvil / Repo Skills / kicad-tools).

Unlike every other /repo:* command, which scans repo / git / filesystem state, this one mines the conversation: the deferred work and discovered bugs that only exist in the session's context. Filing is outward-facing — for upstream targets it writes into other people's repos, usually public ones — so this command is in the same "always confirm first" class as release, remote, and update-tools, never the auto-apply behavior of the hygiene commands. Confirmation is the default and only mode; there is no --ask flag because there is nothing to opt into.

Mining a private session and publishing into a public repo is a visibility boundary crossing, so every cross-repo candidate is scrubbed at authoring time against [[scrub]]'s detection classes before it is ever proposed — see step 3b.

Usage

$repo-followups                 # Review this session, propose issues, confirm, then file
$repo-followups --dry-run       # Propose only — show what would be filed, file nothing
$repo-followups --repo loom     # Restrict to follow-ups targeting one tool repo
$repo-followups --here          # Only this repo; skip all upstream tool repos

Steps

1. Mine the session for candidates

Read the full file on GitHub · 717 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.

2d ago Changed · +10 lines 135b4aada32b
8d ago First seen · 707 lines · 32 tokens per session scan A a3aebd716205

Subscribe to this mod's changes

repo-followups is a skill published in the GitHub repository rjwalters/kicad-tools (73 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 10,173 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-11-01.

Project management

repo-followups next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
repo-followupsrjwalters/kicad-tools	Skill	73	yesterday	MIT	A	32	Claude Code, Codex
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	2d ago	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	100k	today	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	315k	5d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code