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 aeonfun/aeon --skill github-filing-registrygit 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/github-filing-registry)<a href="https://agentmods.dev/skills/aeonfun/aeon/github-filing-registry"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/github-filing-registry/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/aeonfun/aeon/github-filing-registry"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/github-filing-registry.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.00040 | $0.01416 |
| Opus 5.5 | $0.00016 | $0.00566 |
| Sonnet 5.5 | $0.00008 | $0.00283 |
| Haiku 4.5 | $0.00004 | $0.00142 |
Grade A, and why
github-filing-registry 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 today.
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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — Optional. Accepts
owner/repo#Nfor single-item ops, or a subcommand (add,status,triage,sync,log). Empty = run triage.
The filing registry is a structured JSON log at memory/filing-registry.json. Every issue or PR you file against an upstream repo gets an entry so you never file the same thing twice, lose track of what you filed, or forget what happened next.
Registry Schema
{
"version": "1.0",
"last_synced": "2026-05-06T00:00:00Z",
"account": "<your-gh-account>",
"pulls": [],
"issues": [],
"activity_log": []
}
Each entry (in pulls or issues):
{
"id": "owner/repo#123",
"repo": "owner/repo",
"number": 123,
"type": "pr",
"title": "fix: add null check",
"state": "open",
"status": "pending_review",
"next_action": "Await upstream review",
"actions_taken": ["PR filed — fix: add null check"],
"notes": "",
"evidence_tier": "tier_2",
"filed_at": "2026-05-02T00:00:00Z",
"last_action": "2026-05-02T00:00:00Z",
"labels": [],
"url": "https://github.com/owner/repo/pull/123",
"is_upstream": true
}
Activity log entry:
{
"ts": "2026-05-06T00:00:00Z",
"type": "status_update",
"ref": "owner/repo#123",
"desc": "Status changed to: has_fix_pr"
}
Subcommands
add — Register a new filing
./filing-registry add --id owner/repo#N \
--type pr|issue \
--title "fix: add null check" \
--evidence tier_0|tier_1|tier_2|tier_3 \
--url https://github.com/owner/repo/pull/123
Creates a new entry. If the ID already exists, refuses with FILING_EXISTS.
status — Update or inspect an entry
./filing-registry status --id owner/repo#N \
--set needs_attention|pending_review|has_fix_pr|closed|merged|stale \
--next "Await upstream review" \
--action "Pinged maintainer" \
--notes "Confirmed via latest scan"
Reads current entry, applies field updates, appends to actions_taken[], updates last_action.
triage — Show items needing attention
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 157 lines · 40 tokens per session scan A b95b9c6d984f
github-filing-registry is a skill published in the GitHub repository aeonfun/aeon (785 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,416 once invoked, about $0.0002 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-10-30.
Other skills, from other repositories
vignette-todo-run
Run a batch of Vignette TODO items as a multi-agent worktree run. Use when Pete asks to "run the TODOs", "run items N to M", "do a todo run", or hands over queued items from docs/TODOS.md in the Vignette repo. The orchestrator plans, briefs, and reviews; delegated coding agents do every code change and every…
teamboard
Shared team board: claim a work item before starting, hand it over, finish it. The claim is a git-ref lock, so two people cannot take the same item.
close
Wind this window down so it can be closed without losing anything. Stashes this session's own uncommitted edits by explicit path, returns its in-progress Vibe Board tasks, ends the board session with a handoff, and files anything that needs a HUMAN on the human task board. Run when the user types /close, or when a…
engineering-pr
Pull request lifecycle management. Use when you need to create a PR, handle PR reviews, resolve merge conflicts, or manage the PR-to-merge workflow. Extends the engineering skill with GitHub-specific tools and decision framework.
github-issues
Create, triage, label, assign GitHub issues via gh or REST.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…