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 aaronjmars/aeon-agent --skill repo-pulsegit clone --depth 1 https://github.com/aaronjmars/aeon-agentWrote 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/aaronjmars/aeon-agent/repo-pulse)<a href="https://agentmods.dev/skills/aaronjmars/aeon-agent/repo-pulse"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/repo-pulse/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/aaronjmars/aeon-agent/repo-pulse"><img src="https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/repo-pulse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.04349 |
| Opus 5.5 | $0.00019 | $0.01740 |
| Sonnet 5.5 | $0.00010 | $0.00870 |
| Haiku 4.5 | $0.00005 | $0.00435 |
Grade A, and why
repo-pulse 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 2mo 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.
- `gh api` handles auth internally; prefer it over curl. How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — Repo (
owner/repo) to check. If empty, checks all watched repos.
Config
Reads repos from memory/watched-repos.md. Skip any repo whose name ends with -aeon or contains aeon-agent — those are agent repos, not project repos.
If ${var} is set and matches owner/repo, check only that repo.
Context
Read memory/MEMORY.md and the last 4 weeks of memory/logs/ for previous stargazers_count / forks_count per repo. Parse lines matching **owner/repo**: stargazers_count=N, forks_count=M to reconstruct a per-run series — you'll need it for the weekly-baseline (avg4w) used in step 5. Runs are weekly, so expect roughly one datapoint per week; if the logs still hold denser daily entries from the old schedule, take the newest entry in each 7-day bucket rather than mixing cadences.
Steps
1. Compute the 7-day cutoff FIRST
CUTOFF=$(date -u -d '7 days ago' +%Y-%m-%dT%H:%M:%SZ 2>/dev/null || date -u -v-7d +%Y-%m-%dT%H:%M:%SZ)
export CUTOFF
All time filtering uses exactly this timestamp — never "today's date" or "since midnight".
2. Fetch current counts (1 call per repo)
gh api repos/owner/repo --jq '{stargazers_count, forks_count, subscribers_count}'
If this call returns non-2xx (404, 403, rate limit), record source=fail with the reason and continue to the next repo. Do not abort the batch.
3. Fetch recent events — primary input
One call per repo covers stargazers, forks, and releases for the last ~90 days, newest-first:
gh api --paginate "repos/owner/repo/events?per_page=100" \
--jq '[.[] | select(.created_at >= env.CUTOFF) | {type, actor: .actor.login, created_at, tag: (.payload.release.tag_name // null), action: (.payload.action // null)}]'
Paginate — a single 100-event page covers ~24h on an active repo but can truncate a 7-day window. Use --paginate and stop early once you see an event older than CUTOFF (events are newest-first). If the oldest event you retrieved is still newer than CUTOFF, the window is truncated: record truncated=true for that repo and say so in the report — never present a truncated count as complete.
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.
- 2mo ago First seen · 228 lines · 48 tokens per session scan A 6ccea87e3f98
repo-pulse is a skill published in the GitHub repository aaronjmars/aeon-agent (12 stars, last pushed 29d ago), licensed MIT. It adds 48 tokens to every session and 4,349 once invoked, about $0.0002 per session on Opus 5.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-09-05.
repo-pulse compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| repo-pulseaaronjmars/aeon-agent | Skill | 12 | 29d ago | MIT | A | 48 | Claude Code, Codex |
| strategy-specromudille-bit/agentpay | Skill | 4 | yesterday | none | A | 177 | Claude Code |
| agentpay-routeromudille-bit/agentpay | Skill | 4 | yesterday | none | A | 100 | Claude Code |
| agentpay-sessionromudille-bit/agentpay | Skill | 4 | yesterday | none | A | 78 | Claude Code |
| aawpaawp-ai/aawp | Skill | 3 | 8mo ago | none | A | 90 | Claude Code, Codex |
| githubAIOSAI/AIPass | Skill | 317 | 2d ago | MIT | A | 23 | Claude Code |
| darwinia0xSanei/darwinia | Skill | 84 | 7mo ago | MIT | A | 36 | Claude Code, Codex |