repo-pulse

repo-pulse is a skill for Claude Code, Codex from aaronjmars/aeon-agent. It costs 48 tokens per session (4,349 once invoked), scanned A, original, MIT.

A report tool for tracking new stars, forks, and releases on watched GitHub repositories. It also gathers basic public profile details about new stargazers and forkers.

In plain words
What is it for?
Use it to monitor selected repositories, review changes in stars and forks, inspect new contributor profiles, and produce a growth assessment.
Why use it?
It replaces manual repository checks and compares recent growth with earlier weekly activity.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md.

Good fit Use it to monitor selected repositories, review changes in stars and forks, inspect new contributor profiles, and produce a growth assessment.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aaronjmars/aeon-agent/repo-pulse
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 aaronjmars/aeon-agent --skill repo-pulse
Clone the repo
git clone --depth 1 https://github.com/aaronjmars/aeon-agent

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 repo-pulse

README.md
[![agentmods](https://agentmods.dev/badge/skills/aaronjmars/aeon-agent/repo-pulse/github.svg)](https://agentmods.dev/skills/aaronjmars/aeon-agent/repo-pulse)
Your own site
<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.

agentmods 80×15 button for repo-pulse

Your own site · 80×15
<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>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,349 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00048 $0.04349
Opus 5 $0.00024 $0.02174
Sonnet 5 $0.00010 $0.00870
Haiku 4.5 $0.00005 $0.00435

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

Security

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 5d 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.
skills/repo-pulse/SKILL.md · 228 lines

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.

Read the full file on GitHub · 228 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. 5d ago First seen · 228 lines · 48 tokens per session scan A 6ccea87e3f98

Subscribe to this mod's changes

repo-pulse is a skill published in the GitHub repository aaronjmars/aeon-agent (11 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 4,349 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-09-05.

Related

Other skills, from other repositories

github

GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries.

AIOSAI/AIPass · 23 tokens

github

GitHub CLI (gh) for repository management, issues, pull requests, releases, workflows, search, gists, and API access. Use when the user asks about any GitHub operation — creating repos, forking, cloning, PR workflows, issue triage, CI/CD runs, code search, release management, or direct API calls. Keywords: github, gh…

bug-ops/zeph · 104 tokens

rust-agent-handoff

Handoff protocol for the Rust multi-agent development team (rust-architect, rust-developer, rust-testing-engineer, rust-performance-engineer, rust-security-maintenance, rust-code-reviewer, rust-cicd-devops, rust-debugger, rust-critic). Use only when orchestrating subagents via structured YAML files in .local/handoff/.…

bug-ops/zeph · 85 tokens

code-analysis

LSP-based code analysis via mcpls MCP server. Use for compiler-accurate type inspection, go-to-definition, find-all-references, diagnostics, call hierarchy, workspace symbol search, code actions, rename refactoring, and document formatting. Provides real compiler errors — not guesses. Keywords: LSP, language server…

bug-ops/zeph · 105 tokens

git

Run git version control commands for repository management. Use when the user asks to check status, view history or diffs, stage and commit changes, manage branches, merge or rebase, work with remotes, stash changes, tag releases, cherry-pick commits, bisect regressions, resolve conflicts, manage worktrees or…

bug-ops/zeph · 106 tokens

openclaw-dev

OpenClaw Dev Agent — OpenClaw-only docs-aware development assistant. For OpenCoven/coven PR creation, redirect to skills/pr-agent, the Coven PR Readiness Agent.

OpenCoven/coven · 42 tokens