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-refgit 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-ref)<a href="https://agentmods.dev/skills/runkids/feature-radar/feature-radar-ref"><img src="https://agentmods.dev/badge/skills/runkids/feature-radar/feature-radar-ref/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/runkids/feature-radar/feature-radar-ref"><img src="https://agentmods.dev/badge/skills/runkids/feature-radar/feature-radar-ref.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.00134 | $0.00754 |
| Opus 5.5 | $0.00054 | $0.00302 |
| Sonnet 5.5 | $0.00027 | $0.00151 |
| Haiku 4.5 | $0.00013 | $0.00075 |
Grade A, and why
feature-radar-ref 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 27d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Reference
Record external observations into .feature-radar/references/.
Deep Read
Behavioral Directives
Workflow
- Identify the source — ask the user what they observed:
- Interesting project, technique, or creative approach?
- Ecosystem trend or emerging pattern?
- Notable feature or solution from a related project?
- User comparison, feedback, or question?
- Research, article, or talk with relevant insights?
- Gather context — URL, date, key details. If the user provides a GitHub URL, fetch the issue/PR for full context.
- Classify — determine the right file:
- Existing reference file → append a new entry
- New topic → create
.feature-radar/references/{topic}.md
- Assess impact — before writing to references/, answer each question:
- New opportunity or feature idea? → state yes/no, suggest file if yes
- Way to enhance existing features? → state yes/no, suggest update if yes
- Ecosystem trend? → state yes/no, suggest specs/ecosystem-trends.md update if yes
- Checkpoint — State what was written and the impact assessment results. Ask: "I've updated
references/{topic}.md. Does this look correct, or should I adjust anything?" Wait for user confirmation before proceeding. - Update base.md — increment the references count in Tracking Summary
File Format
Use the format defined in ../feature-radar/references/SPEC.md § 3.5 (references/{topic}.md).
Naming Convention
Name by the subject being tracked, not the event:
- Good:
vercel-skills-ecosystem.md,agent-path-conventions.md,cli-ux-patterns.md - Bad:
2026-02-18-update.md,interesting-finding.md
Guidelines
- Always cite source URLs and dates for traceability.
- Append new entries chronologically to existing files — don't create a new file per observation.
- Be objective. Record what happened, then assess implications separately.
- If the observation reveals an unmet need or innovation opportunity, proactively suggest creating an opportunity.
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.
- 27d ago Changed · -9 lines · -65 tokens per session 17def4f13602
- 1mo ago First seen · 88 lines · 199 tokens per session scan A e3a15f868c08
feature-radar-ref is a skill published in the GitHub repository runkids/feature-radar (13 stars, last pushed 27d ago), licensed MIT. It adds 134 tokens to every session and 754 once invoked, about $0.0005 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-30.
Other skills, from other repositories
technical-documentation
Audit, write, and improve developer documentation using Google's Developer Documentation Style Guide and Technical Writing courses. Use this skill for any documentation work, even when the user names no style guide: "audit our docs", "review this README", "write a README", "getting started guide", "how-to or…
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
web-typography
Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "line height", "responsive typography", "web font loading", "type hierarchy", "variable fonts", "FOUT/FOIT", "typographic scale", or "the text is hard to read". Also trigger when choosing between system…
crossing-the-chasm
Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", "pragmatist buyers", "growth stalled…
design-sprint
Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate before we build", "rapid prototype", "test with users", or "should we build this". Also trigger when a team is stuck in endless debate over a high-stakes product…