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 tjboudreaux/cc-plugin-text-visualizations --skill tools-visual-retrogit clone --depth 1 https://github.com/tjboudreaux/cc-plugin-text-visualizationsWrote 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/tjboudreaux/cc-plugin-text-visualizations/tools-visual-retro)<a href="https://agentmods.dev/skills/tjboudreaux/cc-plugin-text-visualizations/tools-visual-retro"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-plugin-text-visualizations/tools-visual-retro.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.00028 | $0.00340 |
| Opus 5 | $0.00014 | $0.00170 |
| Sonnet 5 | $0.00006 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
tools-visual-retro 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 7d 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.
What it actually says
Visual Retro Templates
Intent
- Make retrospective insights digestible for visual learners without slideware.
- Standardize text-based templates for PRs, issues, or shared docs.
Inputs
- Retro categories (Went Well, Risks, Next Bets, Metrics).
- Key quantitative results and qualitative highlights.
- Owners + follow-up items.
Workflow
- Pick template
- Grid:
+------------+------------------+ | Went Well | Needs Attention | +------------+------------------+ | ... | ... | - Timeline w/ milestones.
- Heatmap: use
[]intensity markers ([++],[+],[~],[!]).
- Grid:
- Populate data
- Keep bullet lines short; include metric deltas (
+12% DAU). - Tag owners
(@name)next to action items.
- Keep bullet lines short; include metric deltas (
- Embed artifacts
- Link to logs, dashboards, or experiment IDs inline.
- Distribute
- Paste into PR descriptions, GitHub Discussions, or Slack posts.
- Optionally store canonical version under
.factory/retros/<date>.txt.
- Iterate
- Add “Next Checkpoint” section to set evaluation date.
Verification
- Template fits within 80 characters width; column headers aligned.
- Each action item shows owner + due date.
- Retro artifact linked in change summary or issue comment.
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.
- 7d ago First seen · 43 lines · 28 tokens per session scan A e25f563e540a
tools-visual-retro is a skill published in the GitHub repository tjboudreaux/cc-plugin-text-visualizations (2 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 340 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…