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/sandsower/beislid/retronpx skills add sandsower/beislid --skill retrogit clone --depth 1 https://github.com/sandsower/beislidWrote 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/sandsower/beislid/retro)<a href="https://agentmods.dev/skills/sandsower/beislid/retro"><img src="https://agentmods.dev/badge/skills/sandsower/beislid/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 | $0.00081 | $0.01271 |
| Opus 5 | $0.00041 | $0.00635 |
| Sonnet 5 | $0.00016 | $0.00254 |
| Haiku 4.5 | $0.00008 | $0.00127 |
Grade A, and why
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 3d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retro
Turn a run or session into workflow-improvement recommendations. retro answers: what should change about this repo's Beislið workflow after what we just learned?
retro is recommendation-only. It never edits .beislid/workflow.md; setup remains the canonical config writer.
Use this for:
- Post-run/session reflection
- Gate tuning suggestions
- Workflow default refinement
- Reviewing skipped, noisy, missing, slow, or ambiguous workflow steps
- Preparing a handoff for a later
setuprun
Do not use this for:
- Checking whether config is valid or probes pass — use
doctor - Direct config editing — use
setup - Product shaping — use
spec - PR readiness gates — use
ready-for-review
Process
1. Load available context
Inspect before interviewing. Use what the current host and repo provide, then ask only for missing high-value context.
Collect, when available:
- Current user request and any extra notes they supplied
- Current session context, including recent gate/review/setup friction already visible in chat
- Git repo root, branch, status, and changed-file summary
<repo>/.beislid/workflow.mdas the current workflow baseline.beislid/checkpoints/latest.jsonand readable referenced checkpoint artifacts- Beislið run-ledger summaries or final reports for relevant recent runs, if the CLI/state is available
- Session-memory or memento notes, if the host exposes memory/search tools
- Recent local evidence such as gate output summaries, skipped checks, accepted risks, or repeated manual prompts
If a source is missing, unavailable, stale, or too expensive to inspect, say so briefly and continue with the evidence you have. Do not fail solely because durable context is absent.
2. Compare evidence to workflow config
Review the whole workflow, not just gates. Look for friction in:
- ticket source and branch detection
- scopes, gate sets, gate metadata, cost, selectors, and parallel-safety hints
- lifecycle/checkpoint artifacts
- action policy prompts or unsafe defaults
- PR review/update paths
- final check and review handoff behavior
- model routing disclosures or repeated model-fit issues
- setup/doctor discoverability gaps
- prose in
workflow.mdthat should encode a default, warning, or team preference
What ships with it
2 files 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.
- 3d ago First seen · 133 lines · 81 tokens per session scan A a7d871504ec2
retro is a skill published in the GitHub repository sandsower/beislid (10 stars, last pushed 4d ago), licensed MIT. It adds 81 tokens to every session and 1,271 once invoked, about $0.0004 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…