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-scangit 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-scan)<a href="https://agentmods.dev/skills/runkids/feature-radar/feature-radar-scan"><img src="https://agentmods.dev/badge/skills/runkids/feature-radar/feature-radar-scan.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.00232 | $0.02335 |
| Opus 5 | $0.00116 | $0.01167 |
| Sonnet 5 | $0.00046 | $0.00467 |
| Haiku 4.5 | $0.00023 | $0.00233 |
Grade A, and why
feature-radar-scan 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scan Opportunities
Discover new feature opportunities and add them to .feature-radar/opportunities/.
Deep Read
Behavioral Directives
Additional directive for this skill:
- Filter aggressively — Do NOT create opportunity files for weak signals. If you can't cite concrete demand evidence, skip it.
Brainstorm Intake
Enter Brainstorm Intake if ANY of these are true:
- User says "I have an idea", "what if we...", "I was thinking about...", "brainstorm"
- User describes a problem without a clear feature shape
- User's input lacks specific demand signals, impact/effort estimates, or a concrete feature name
Skip Brainstorm Intake if ALL of these are true:
- User gave a specific directive like "scan opportunities", "scan ecosystem", "find new features"
- User's input does not contain a personal idea or vague exploration
If skipping, jump directly to ## Workflow.
Phase 1: Core Questions
Ask these one at a time. Prefer multiple-choice when possible.
- Problem space — "What problem are you trying to solve, or what experience do you want to improve?"
- Cross-reference: search existing
opportunities/andarchive/for related themes. - If a match is found, surface it: "Is this related to #{nn} {title}, or a completely different direction?"
- Cross-reference: search existing
- Target user — "Who would benefit from this feature?"
- Offer choices derived from
base.mdProject Context if available.
- Offer choices derived from
- Spark — "What triggered this idea?"
- (A) A pain point from my own usage
- (B) Saw a similar feature in another tool/project
- (C) New technical possibilities (new API, new library)
- (D) Community/user feedback
- (E) Pure creative exploration
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 · 213 lines · 232 tokens per session scan A 3163bedd3383
feature-radar-scan is a skill published in the GitHub repository runkids/feature-radar (13 stars, last pushed 6mo ago), licensed MIT. It adds 232 tokens to every session and 2,335 once invoked, about $0.0012 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-asset-management
CRE Asset Management analysis suite — 9 specialist skills for post-acquisition multifamily operations including annual budgeting, monthly variance analysis, rent collection, renewal decisions, lease-up tracking, capex execution, NOI improvement, hold/sell/refi scenario analysis, and quarterly asset review memos.
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.
cre-lender-credit
CRE Lender/Credit analysis suite - 8 specialist skills for U.S. CRE loan screening and sizing, sponsor and appraisal review, credit memo writing, annual risk rating, covenant and watchlist monitoring, problem loans, and portfolio stress testing.
cre-retail
CRE Retail analysis suite - 8 specialist skills for U.S. retail trade-area studies, rent roll and tenant mix, lease abstraction, co-tenancy and anchor risk, CAM recovery, underwriting, financing fit, and investment committee memo writing.
cre-brokerage
CRE Brokerage Investment Sales v1 - 8 specialist skills for U.S. seller-side commercial investment sales brokers, covering assignment intake, broker opinion of value, listing proposal, OM and teaser drafting, buyer process management, bid leveling, negotiation support, and PSA-to-close coordination.
cre-capital-markets
CRE Capital Markets and Debt Maturity suite - 8 specialist skills for maturity diagnostics, refinance proceeds gaps, extensions, workouts, rescue capital, term sheet comparison, CMBS special servicing readiness, lender updates, and recap IC memos.