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 agentmods add skills/jeremydev87/codingbuddy/retronpx skills add JeremyDev87/codingbuddy --skill retrogit clone --depth 1 https://github.com/JeremyDev87/codingbuddyWhat 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 | $0.00036 | $0.01826 |
| Opus 5 | $0.00018 | $0.00913 |
| Sonnet 5 | $0.00007 | $0.00365 |
| Haiku 4.5 | $0.00004 | $0.00183 |
Grade B, and why
retro scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -rl "[keyword]" ~/.claude/projects/*/memory/ 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Structured Retrospective
Analyze what happened in the current session, extract learnings, and turn them into durable improvements — rules, feedback memories, or GitHub issues.
Follow every step in order. Stop and report if any step fails.
Core Principle
Learnings decay. If a retrospective doesn't happen immediately after the work, the insights are lost. Capture them while context is fresh, classify them by type, and route them to the right destination so they compound over time.
The Iron Law
NO RETRO WITHOUT EVIDENCE.
Every Keep, Problem, and Action must cite a specific event from the session — not a general feeling.
When to Use
- After completing parallel/batch work (taskmaestro waves, swarm, ultrawork)
- After a multi-step plan execution (PLAN → ACT → EVAL cycle)
- After a significant debugging session
- After any session where something surprising happened (good or bad)
- When the user explicitly asks to reflect on recent work
Don't use when:
- The session was trivial (single file edit, quick fix)
- No context.md or session history exists to analyze
Step 1: Gather Session Context
Read the session history from docs/codingbuddy/context.md:
cat docs/codingbuddy/context.md
If the file does not exist or is empty, check for alternative sources:
$ARGUMENTS— the user may pass a file path or description- Git log for recent commits on the current branch:
git log --oneline -20 - If no context is found, stop and tell the user: "No session history found. Run a PLAN → ACT cycle first, or pass a context file as argument."
Collect:
- Tasks attempted — what was planned
- Tasks completed — what actually shipped
- Tasks failed or blocked — what didn't work and why
- Timeline — rough sequence of events
Step 2: Keep Analysis
Identify what went well. For each item:
| Field | Description |
|---|---|
| What | The specific thing that worked |
| Evidence | Where in the session this happened (commit, step, decision) |
| Why it worked | Root cause of success — not luck, but a reproducible reason |
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 First seen · 243 lines · 36 tokens per session scan B d448c2a650df
retro is a skill published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,826 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
mentor
Use when the user accepts, reviews, or asks about non-trivial code — their own or AI-generated — and should understand it rather than just ship it. Triggers on "mentor", "teach me", "explain this", "quiz me", or right after generating concurrency / security / DB-query / algorithm / auth code. Runs a comprehension loop…
customizations-in-the-agent-host
Architecture and hard-won debugging lessons for customization enablement (plugins, MCP servers, agents, skills, instructions) in the agent host. Use when changing how customizations are discovered, published, enabled/disabled, or handed to a provider SDK; when a customization shows the wrong enabled state in the UI…
om-integration-builder
Build integration provider packages for the Open Mercato Integration Marketplace (payment, shipping, data-sync, webhook). Scaffolds the npm package, adapter, credentials, widget injection, webhook processing, health checks, i18n, tests. Triggers on "build integration", "add provider", "integrate with…
om-auto-qa-scenarios
Generate a human QA report for a window of merged PRs (date floor, PR-number floor, or default last 7 days) and ship it as a docs-only PR against develop. Groups work into P0/P1/P2 testing routes with click paths, verification points, and risk callouts. Writes markdown + HTML under .ai/analysis/. Hands off to…
om-backend-ui-design
Design and implement consistent, production-grade backend/backoffice interfaces using the @open-mercato/ui component library. Use this skill when building admin pages, CRUD interfaces, data tables, forms, detail pages, or any backoffice UI components. Ensures visual consistency and UX patterns across all application…
om-implement-spec
Implement a specification (or specific phases) using coordinated subagents with unit tests, integration tests, docs, and code-review compliance. Tracks progress by updating the spec. Triggers on "implement spec", "implement phases", "build from spec", "code the spec".