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-dogit 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-do)<a href="https://agentmods.dev/skills/shortcuts/radin/radin-do"><img src="https://agentmods.dev/badge/skills/shortcuts/radin/radin-do/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-do"><img src="https://agentmods.dev/badge/skills/shortcuts/radin/radin-do.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.00030 | $0.00517 |
| Opus 5.5 | $0.00012 | $0.00207 |
| Sonnet 5.5 | $0.00006 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
radin-do 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 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.
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
Run One Prompt
A front door for one piece of work: record it, optionally plan it, run the loop on that one task.
Step 1: Record
Invoke /radin-record with the user's prompt as a specific ask, plus one
instruction: log exactly one entry, never split it, no dependencies. Record's
slicing check and grilling run; its batch gate is skipped for a one-entry
specific ask. A prompt too big for one slice still gets one entry; tell the
user to use /radin-record for large work.
Take the new entry's id from the add output. With only a title, run
RADIN_CLI backlog find "<title>".
Step 2: Plan or implement
Ask with AskUserQuestion: Plan it first or Implement directly.
- Implement directly: go to Step 3.
- Plan it first: invoke
/radin-planon the id and plan the entry as one unit. Show the user a summary of the plan's Outcome and Decisions, then ask withAskUserQuestion:Execute,I have feedback, orStop.Execute: go to Step 3.- Feedback: invoke
/mattpocock-skills:grillingon the plan's open decisions, revise the plan file in place, show the summary again, and ask again. Loop untilExecuteorStop.
Stop at any round in Steps 1 and 2: run RADIN_CLI backlog remove "<id>",
report the removal, run nothing.
Step 3: Run the loop
Read RADIN_LIB/radin-run.md in full now and follow it as this skill's body.
Re-read it after any compaction. The invoking scope is the task id from Step 1.
No-plan rule
Call task-next and task-report --next with no other flag. Every task then
comes back as kind execution, and a task with a plan implements from that
plan.
Reply: the run loop's Phase 5 summary, verbatim; or, after a stop, the
removal line from backlog remove.
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 · 53 lines · 30 tokens per session scan A bbae0d8773bb
radin-do is a skill published in the GitHub repository shortcuts/radin (5 stars, last pushed 3d ago), licensed MIT. It adds 30 tokens to every session and 517 once invoked, about $0.0001 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-10-14.
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.
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.