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 adrielp/ai-engineering-harness --skill github-trackergit clone --depth 1 https://github.com/adrielp/ai-engineering-harnessWrote 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/adrielp/ai-engineering-harness/github-tracker)<a href="https://agentmods.dev/skills/adrielp/ai-engineering-harness/github-tracker"><img src="https://agentmods.dev/badge/skills/adrielp/ai-engineering-harness/github-tracker/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/adrielp/ai-engineering-harness/github-tracker"><img src="https://agentmods.dev/badge/skills/adrielp/ai-engineering-harness/github-tracker.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.00204 | $0.02175 |
| Opus 5.5 | $0.00082 | $0.00870 |
| Sonnet 5.5 | $0.00041 | $0.00435 |
| Haiku 4.5 | $0.00020 | $0.00217 |
Grade A, and why
github-tracker 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 1mo 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.
The `gh` CLI must be installed and authenticated (`gh auth status` should succeed). All commands use `gh` — never raw `curl` with tokens. How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Tracker
Surface GitHub pull requests, issues, notifications, and project board items that need attention using the gh CLI.
Read-Only Safety Constraint
This skill is strictly read-only. NEVER execute any gh command that creates, modifies, or deletes GitHub resources. This means:
Allowed: gh search, gh pr view, gh issue view, gh pr checks, gh api (GET requests), gh api graphql (queries only), gh repo list, gh pr list, gh issue list, gh notification list
Forbidden: gh pr create, gh pr merge, gh pr close, gh pr edit, gh pr review, gh issue create, gh issue close, gh issue edit, gh pr comment, gh issue comment, gh api -X POST/PUT/PATCH/DELETE (any mutating HTTP method), any GraphQL mutations, or any other command that writes data to GitHub.
If the user asks you to take an action on GitHub (merge a PR, comment on an issue, close something), tell them this skill is read-only and they should do it themselves in the GitHub UI or CLI.
Prerequisites
The gh CLI must be installed and authenticated (gh auth status should succeed). All commands use gh — never raw curl with tokens.
Before running any commands, verify gh is available:
gh auth status
If this fails, tell the user to install and authenticate gh: https://cli.github.com/
Getting the Current User
Never hardcode a username. Always resolve it dynamically:
gh api user --jq '.login'
Cache the result in a variable for the session.
Core Workflows
1. PRs Needing My Attention
This is the most common ask. "Attention" means multiple things — combine these signals:
a) Review requests (highest priority):
gh search prs --review-requested=@me --state=open --json repository,title,number,url,updatedAt,labels --limit 50
b) PRs where I'm mentioned or assigned:
gh search prs --mentions=@me --state=open --json repository,title,number,url,updatedAt --limit 30
gh search prs --assignee=@me --state=open --json repository,title,number,url,updatedAt --limit 30
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.
- 1mo ago First seen · 222 lines · 204 tokens per session scan A 6c0de066bb86
github-tracker is a skill published in the GitHub repository adrielp/ai-engineering-harness (22 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 204 tokens to every session and 2,175 once invoked, about $0.0008 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-08-30.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
cuga-github-issues
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…
implement-issue
Implement a Linear brief in a named GitHub repo. Use when the brief skill is implement-issue or the user wants a new branch and draft PR.