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 agentmods add skills/aeonfun/aeon/bd-radarnpx skills add aeonfun/aeon --skill bd-radargit clone --depth 1 https://github.com/aeonfun/aeonWrote 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/aeonfun/aeon/bd-radar)<a href="https://agentmods.dev/skills/aeonfun/aeon/bd-radar"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/bd-radar.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 | $0.00038 | $0.03030 |
| Opus 5 | $0.00019 | $0.01515 |
| Sonnet 5 | $0.00008 | $0.00606 |
| Haiku 4.5 | $0.00004 | $0.00303 |
Grade A, and why
bd-radar scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
GitHub: forks/issues of your repos are fetched **in-run** via `./secretcurl` against `api.github.com` with the read-only `GH_READ_PAT` (the `{GH_READ_PAT}` placeholder keeps the secret off the command line), which reads Copies of this mod
1 near-identical copy found in the catalogue:
- bd-radar — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — Optional.
dry-runskips notify (state + leads still update). Empty = normal run.
Today is ${today}. Read STRATEGY.md and memory/MEMORY.md. Read memory/products.md for your repos, handles, and search terms. If soul/SOUL.md + soul/STYLE.md are populated, write in the operator's voice; otherwise neutral.
Why this exists
The north-star is builders shipping on your products. BD signal — a fork that actually runs, a repo that ships an extension on top of you, someone asking "can I integrate", a project quote-tweeting one of your handles — arrives scattered across GitHub, X, HN and Reddit, and usually reaches the operator weeks late, through the timeline, after the moment to engage has passed. bd-radar is the standing sweep that catches each inbound the day it appears and turns it into a named lead with a suggested next move — so you reach out while it's warm. This is "chase users, investors follow" wired into cron.
Config — memory/products.md
Shared config (see product-pulse for the full format). bd-radar uses, per product: the repos (to find forks/issues), the handles (to find mentions/quote-tweets), and the terms (the product-name / tagline strings to search GitHub, X, HN, Reddit). If memory/products.md is missing or empty, log BD_RADAR_NO_PRODUCTS_CONFIG and fall back to memory/watched-repos.md for repos + STRATEGY.md for the wedge; X/term search is skipped with no config.
What counts as a BD lead (signal taxonomy)
Ranked strongest → weakest. Tag each lead with its class:
| Class | Signal | Why it matters |
|---|---|---|
building |
New ecosystem repo / extension that runs on or builds on one of your products | Already shipped — highest intent, partner candidate |
forking |
New fork of one of your repos with its own commits (not a drive-by star) | Active builder — likely to ship next |
integrating |
Issue/PR/discussion asking to integrate, or a repo importing your API/SDK | Explicit ask — fastest to convert |
mentioning |
A project/builder account (not a random) posting about your products on X/HN/Reddit | Warm — worth a reply or DM |
adjacent |
A team in your wedge (the space your products occupy — see STRATEGY.md / the surface lines in products.md) doing relevant work |
Outbound candidate — you reach out |
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.
- 4d ago First seen · 124 lines · 38 tokens per session scan A 7cfcdc670fce
bd-radar is a skill published in the GitHub repository aeonfun/aeon (714 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 3,030 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
summarize
Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.