feature-radar-archive

feature-radar-archive is a skill for Claude Code, Codex from runkids/feature-radar. It costs 213 tokens per session (986 once invoked), scanned A, original, MIT.

A workflow for archiving a feature after it is finished, rejected, already covered, deferred, or found not to apply. It records the decision and extracts lessons for future project work.

In plain words
What is it for?
Use it when a feature reaches a final state to move its record into `.feature-radar/archive/`, document learnings, and identify related opportunities or ecosystem changes.
Why use it?
It prevents completed feature decisions and their reasoning from disappearing, while keeping the project's feature-tracking files up to date.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when a feature reaches a final state to move its record into .feature-radar/archive/, document learnings, and identify related opportunities or ecosystem changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/runkids/feature-radar/feature-radar-archive
Install

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.

Any agent
npx skills add runkids/feature-radar --skill feature-radar-archive
Clone the repo
git clone --depth 1 https://github.com/runkids/feature-radar

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for feature-radar-archive

README.md
[![agentmods](https://agentmods.dev/badge/skills/runkids/feature-radar/feature-radar-archive.svg)](https://agentmods.dev/skills/runkids/feature-radar/feature-radar-archive)
Your own site
<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>
Per session 213 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 986 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 8d ago against content hash 5a21e255a083, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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.

skills/feature-radar-archive/SKILL.md · 103 lines

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

  1. Identify the feature — ask the user which feature to archive. Check opportunities/ for an existing file to move.

  2. 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
  3. Create archive file — write .feature-radar/archive/{nn}-{slug}.md

  4. Checkpoint — Review & Annotate per ../feature-radar/references/WORKFLOW-PATTERNS.md

  5. 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
  1. Remove from opportunities — if the feature had an opportunities/ file, delete it
  2. 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} |

Read the full file on GitHub · 103 lines

Changes

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.

  1. 8d ago First seen · 103 lines · 213 tokens per session scan A 5a21e255a083

Subscribe to this mod's changes

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.

Related

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.

ahacker-1/cre-agent-skills · 52 tokens

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…

EAIconsulting/cowork-skills-library · 105 tokens

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.

nexu-io/open-design · 52 tokens

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

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…

wondelai/skills · 147 tokens

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…

pedrohcgs/claude-code-my-workflow · 132 tokens