Borrowing it
Nothing to install: this file belongs to Ducksss/codex-profiles. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Ducksss/codex-profiles/main/.agents/skills/github-monitoring/SKILL.mdgit clone --depth 1 https://github.com/Ducksss/codex-profilesWrote 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/ducksss/codex-profiles/github-monitoring)<a href="https://agentmods.dev/skills/ducksss/codex-profiles/github-monitoring"><img src="https://agentmods.dev/badge/skills/ducksss/codex-profiles/github-monitoring.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.1 | $0.00046 | $0.01129 |
| Opus 5 | $0.00023 | $0.00564 |
| Sonnet 5 | $0.00009 | $0.00226 |
| Haiku 4.5 | $0.00005 | $0.00113 |
Grade A, and why
github-monitoring 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 yesterday.
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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Monitoring
Purpose
Recheck existing GitHub outreach work, reconcile the tracker, and route any new work back to the correct phase. This skill does not create leads or drafts.
Required Context
Read policy gates in ops/outreach/launch.md, the live tracker target, and the
existing PR, issue, listing, or submission URL. Load references/status-map.md
before updating status.
Boundaries
- Recheck existing PRs, issues, listings, and tracker target links.
- Update tracker
Targetsand appendLogentries only. - Use
Log.Workflow = monitoringfor every meaningful recheck. - Do not discover new leads.
- Do not draft PRs, issues, comments, emails, DMs, forum posts, listing submissions, or maintainer replies.
- Do not submit, open, post, comment, email, DM, or otherwise contact externally.
Accepted Input
- Consume targets in
Issue Open,PR Open, orPending Reviewwith a recorded external URL and a dated recheck due inNext Action. - Also consume recheckable
Deferredtargets andListedtargets due for link verification. A missing or inaccessible external URL is a repair input when the target or its history identifies the external work; it is not grounds to replace or delete the platform record. - Monitoring may route to
Run closing draftorRun lead qualification, but it never performs those phases itself.
Tracker Protocol
Create a unique run-<UTC-timestamp>-<random-suffix> <run-id> and list each
accepted status independently. Inspect the external state read-only, then claim
the target immediately before writing reconciliation results:
node scripts/outreach-tracker.mjs list --status "Issue Open" --json
node scripts/outreach-tracker.mjs list --status "PR Open" --json
node scripts/outreach-tracker.mjs list --status "Pending Review" --json
node scripts/outreach-tracker.mjs list --status Deferred --json
node scripts/outreach-tracker.mjs list --status Listed --json
node scripts/outreach-tracker.mjs get <key> --json
node scripts/outreach-tracker.mjs claim <key> --by <run-id>
What ships with it
2 files 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.
- yesterday Changed d7f6cce1e24d
- 2d ago Changed de637a5a8134
- 7d ago First seen · 106 lines · 46 tokens per session scan A 42f2bbf707a4
github-monitoring is a skill published in the GitHub repository Ducksss/codex-profiles (117 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 1,129 once invoked, about $0.0002 per session on Opus 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-08-30.
Other skills, from other repositories
work
Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.
do
Work an increment task by task through the ledger: task next, claim, implement, commit, task done with evidence. Use when saying "implement", "start working", or "continue increment".
sync
One sync surface for GitHub, Jira and Azure DevOps: push progress, pull or import issues, check health, run setup. Use when saying "sync", "push to GitHub", or "import issues".
aigon-next
Suggest the most likely next workflow action based on current context.
gh
You have access to gh (GitHub CLI) for repository and project management.
aigon-feature-reset
Reset feature - remove worktrees, branches, state, and return lifecycle to backlog.