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 shortcuts/radin --skill radin-recordgit clone --depth 1 https://github.com/shortcuts/radinWrote 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/shortcuts/radin/radin-record)<a href="https://agentmods.dev/skills/shortcuts/radin/radin-record"><img src="https://agentmods.dev/badge/skills/shortcuts/radin/radin-record/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.
<a href="https://agentmods.dev/skills/shortcuts/radin/radin-record"><img src="https://agentmods.dev/badge/skills/shortcuts/radin/radin-record.svg" alt="Reviewed on agentmods" width="80" 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.00057 | $0.02047 |
| Opus 5.5 | $0.00023 | $0.00819 |
| Sonnet 5.5 | $0.00011 | $0.00409 |
| Haiku 4.5 | $0.00006 | $0.00205 |
Grade A, and why
radin-record 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 today.
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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Record to Backlog
Step 1: Decide what to log
The instruction sets the scope:
- Specific: "add the auth timeout bug", "fix this issue", "work on adding that feature"
- Generic: "add the findings", "record everything", "we should probably": scan the whole session for anything a reasonable person calls a bug, follow-up, idea, or feedback. Each distinct item becomes its own entry.
Log the entry worded close to how it was raised.
One raised thing can be several sequential pieces of work ("add rate limiting on top of new auth middleware" needs the middleware first). Log each piece as its own entry, sized as a vertical slice:
- It cuts a narrow but COMPLETE path through every layer it touches.
- Landed, it is demoable or verifiable on its own.
- It fits one fresh context window.
- A prefactor, the restructuring that makes the real change easy, is its own entry, which every entry needing it depends on.
One mechanical change whose blast radius fans across the codebase is the exception, so log it as one entry per batch the change breaks, plus a final entry that puts the tree back green depending on every batch.
An item too fuzzy to phrase as a sharp question is a stub ("figure out caching at some point"): log one stub over the whole area, its body saying what is unspecified and what is known, rather than pre-slicing it. Step 2 sharpens it later. A question you can state precisely is an ordinary entry, blocked or not.
An external ticket as context (optional)
A ticket key, Jira or GitHub issue URL: fetch it through the MCP if possible, and treat the ticket as extension to the user's prompt. No MCP or API access: log from the ask alone, and continue.
Step 2: Chart each item's open decisions
Settle judgment calls here, while the user is present.
Apply RADIN_LIB/radin-open-decisions.md to each item. Note each Fact in the entry
body as an open fact to verify. Ask the item's Decisions now, before the next item
and before Step 5's batch list. Keep every settled answer for Step 5's body. An
item with no Decision asks nothing, and so does a stub, one deliberately deferred
whole.
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.
- today Changed · +16 lines f37342692d18
- 2d ago Changed · -7 lines 44ce9fec7857
- 4d ago Changed · -6 lines cbe76a1cf743
- 6d ago Changed 68b37456a307
- 8d ago Changed · +5 lines e31361f97606
- 10d ago Changed · -1 lines 7388ab925270
- 27d ago Changed · -1 lines · -27 tokens per session 89c006b5aa99
- 29d ago Changed · -1 lines 59dc5e0c70e2
- 1mo ago Changed · -1 lines · -15 tokens per session f9fadc8660fc
- 1mo ago First seen · 185 lines · 99 tokens per session scan A 1314d3bdcc55
radin-record is a skill published in the GitHub repository shortcuts/radin (6 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 2,047 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
git-flow
Use when committing, branching, opening PRs, or deciding merge/branch strategy.
lead-orchestration
Use when you are the LEAD (main session) and an owner request arrives that needs agents -- intake, routing, briefs, follow-up, blocks, verification, learning, report. Canonical procedure from request to verified report; not for sub-agents executing a brief.
managing-product
Extracts product requirements and produces a PRD. Use when a user wants to build software and needs to define what to build before architecture or implementation, when scoping an MVP, or when translating a vague idea into a buildable specification.
orchestrating-work
Principles for multi-agent workflow execution. Use when coordinating agents, accepting or rejecting agent work, executing producer-critic cycles, or running any multi-phase orchestrated task.
run-agent
Launch and supervise Claude Code or Codex through the CCAM Run API. Use when the user wants to start a monitored agent, select a model, approval policy, sandbox, or working directory, send a follow-up, inspect live output, resume a native session, or stop a dashboard-launched run.
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…