github-filing-registry

github-filing-registry is a skill for Claude Code, Codex from aeonfun/aeon. It costs 40 tokens per session (1,416 once invoked), scanned A, original, MIT.

A structured record for tracking issues and pull requests filed across upstream GitHub repositories, including their status, evidence, next action, and history.

In plain words
What is it for?
Use it to add, inspect, triage, synchronize, and log upstream issues and pull requests through the GitHub command-line tool.
Why use it?
It prevents duplicate filings and keeps follow-up work visible after an issue or pull request has been sent to another repository.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to add, inspect, triage, synchronize, and log upstream issues and pull requests through the GitHub command-line tool.

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

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 github-filing-registry

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

agentmods 80×15 button for github-filing-registry

Your own site · 80×15
<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>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,416 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00040 $0.01416
Opus 5.5 $0.00016 $0.00566
Sonnet 5.5 $0.00008 $0.00283
Haiku 4.5 $0.00004 $0.00142

Measured today against content hash b95b9c6d984f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

skills/github-filing-registry/SKILL.md · 157 lines

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#N for 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

Read the full file on GitHub · 157 lines

Files

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.

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. today First seen · 157 lines · 40 tokens per session scan A b95b9c6d984f

Subscribe to this mod's changes

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.

Related

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…

petekp/claude-code-setup · 141 tokens

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.

byerlikaya/claude-starter-kit · 38 tokens

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…

HuntsDesk/ve-kit · 87 tokens

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.

sweatco/archie-hq · 48 tokens

github-issues

Create, triage, label, assign GitHub issues via gh or REST.

john-data-chen/hermes-agent-backup · 20 tokens

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…

microsoft/agent-framework · 102 tokens