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 runkids/feature-radar --skill feature-radar-archivegit clone --depth 1 https://github.com/runkids/feature-radarWrote 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/runkids/feature-radar/feature-radar-archive)<a href="https://agentmods.dev/skills/runkids/feature-radar/feature-radar-archive"><img src="https://agentmods.dev/badge/skills/runkids/feature-radar/feature-radar-archive.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.00213 | $0.00986 |
| Opus 5 | $0.00106 | $0.00493 |
| Sonnet 5 | $0.00043 | $0.00197 |
| Haiku 4.5 | $0.00021 | $0.00099 |
Grade A, and why
feature-radar-archive 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 8d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archive Feature
Move a feature to .feature-radar/archive/ and run the mandatory extraction checklist.
Deep Read
Behavioral Directives
Workflow
-
Identify the feature — ask the user which feature to archive. Check
opportunities/for an existing file to move. -
Determine status:
- Done — fully implemented and working
- Covered — existing functionality handles the use case
- Rejected — decided against implementing
- N/A — not applicable to our architecture
- Deferred — valuable but postponed with rationale
-
Create archive file — write
.feature-radar/archive/{nn}-{slug}.md -
Checkpoint — Review & Annotate per
../feature-radar/references/WORKFLOW-PATTERNS.md -
Run extraction checklist:
Extraction Checklist
□ archive/{nn}-{slug}.md created with correct status □ Extract learnings → specs/{topic}.md □ Derive new opportunities → opportunities/{nn}-{slug}.md □ Update references → references/{topic}.md □ Update ecosystem trends → specs/ecosystem-trends.md
Acceptable responses per check:
- "No learnings to extract" — acceptable, but must be stated
- "New opportunity identified: {description}" — create the file
- "No reference updates needed" — acceptable, but must be stated
- Remove from opportunities — if the feature had an
opportunities/file, delete it - Update base.md — adjust counts in Tracking Summary
Checkpoint: Present extraction results using this format:
Archive: {nn}-{slug} ({status})
| Check | Result |
|-------|--------|
| Learnings | {created specs/X.md / updated specs/X.md / none} |
| Opportunities | {created opportunities/X.md / none} |
| References | {updated references/X.md / none} |
| Ecosystem | {updated specs/ecosystem-trends.md / none} |
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.
- 8d ago First seen · 103 lines · 213 tokens per session scan A 5a21e255a083
feature-radar-archive is a skill published in the GitHub repository runkids/feature-radar (13 stars, last pushed 6mo ago), licensed MIT. It adds 213 tokens to every session and 986 once invoked, about $0.0011 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-30.
Other skills, from other repositories
cre-development
CRE Development and Construction suite - 8 specialist skills for U.S. site/entitlement screening, budget and yield-on-cost, construction loan sizing, GC contracts, draw review, schedule risk, lease-up pro forma, and IC memo writing.
client-context-system
Sets up a complete per-client workspace in Cowork with isolated context, preferences, deliverable templates, running notes, decision log, and automatic status reporting. For consultants, agencies, and professional services. Useful when onboarding a new client, during engagement kickoffs, for organizing existing client…
html-ppt-knowledge-arch-blueprint
OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…