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 MotWakorb/ai-agent-dev-team --skill retro-syncgit clone --depth 1 https://github.com/MotWakorb/ai-agent-dev-teamWrote 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/motwakorb/ai-agent-dev-team/retro-sync)<a href="https://agentmods.dev/skills/motwakorb/ai-agent-dev-team/retro-sync"><img src="https://agentmods.dev/badge/skills/motwakorb/ai-agent-dev-team/retro-sync.svg" alt="Measured on agentmods" 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.00055 | $0.00865 |
| Opus 5 | $0.00028 | $0.00432 |
| Sonnet 5 | $0.00011 | $0.00173 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
retro-sync 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 6d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retro Sync
Push local retros in ~/retros/ to the shared learning corpus: https://github.com/EndofLineTech/retros (public). Push-only — pulling the corpus down for analysis is /retro-mine's job. Retros are pseudonymized — the corpus is about process lessons, not about whose project it was.
Process
-
Bootstrap (only if
~/retrosis not already a git repo):git -C ~/retros init -b main git -C ~/retros remote add origin https://github.com/EndofLineTech/retros.git git -C ~/retros fetch origin -
Project map —
~/.claude/retro-project-map.txtholds stable pseudonyms, onereal-name=pseudonymper line:acme-billing=project-a ai-agent-dev-team=project-bCheck that every project referenced by the retros being synced has an entry. If one is missing, assign the next unused
project-<letter>and append it. The map is local and private — never commit it, never mention real names in the retro repo. Ceiling: the map is per-machine; keep it consistent across your machines by copying it once (it changes rarely). -
Scrub — run the scrub script that lives next to this SKILL.md:
bash <skill-dir>/scrub.sh ~/retrosIt applies, in place: project-map pseudonymization (content and filenames), then redaction of emails, IPs, private keys, common credential formats (AWS, GitHub, Anthropic/OpenAI, Slack, bearer tokens), then any literal strings in
~/.claude/retro-scrub.txt(one per line — client names, employer names, internal hostnames). -
Review — if the scrub redacted anything (
[REDACTED],[EMAIL], key markers — pseudonym renames don't count), show the user what and where. A redaction hit means the retro-writing rules leaked something; name the category so the rules can be tightened. -
Commit and push (no hostnames or usernames in the commit message):
git -C ~/retros add -A git -C ~/retros commit -m "retro sync: <n> retro(s)" git -C ~/retros pull --rebase origin main # prerequisite for the push, not a gathering step git -C ~/retros push -u origin mainNothing staged and nothing unpushed → stop; there's nothing to sync.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 58 lines · 55 tokens per session scan A f7ab1bfdf566
retro-sync is a skill published in the GitHub repository MotWakorb/ai-agent-dev-team (2 stars, last pushed 24d ago), licensed MIT. It adds 55 tokens to every session and 865 once invoked, about $0.0003 per session on Opus 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".