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 anotherben/claude-harness --skill gh-issuesgit clone --depth 1 https://github.com/anotherben/claude-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/anotherben/claude-harness/gh-issues)<a href="https://agentmods.dev/skills/anotherben/claude-harness/gh-issues"><img src="https://agentmods.dev/badge/skills/anotherben/claude-harness/gh-issues/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/anotherben/claude-harness/gh-issues"><img src="https://agentmods.dev/badge/skills/anotherben/claude-harness/gh-issues.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.00046 | $0.01604 |
| Opus 5.5 | $0.00018 | $0.00642 |
| Sonnet 5.5 | $0.00009 | $0.00321 |
| Haiku 4.5 | $0.00005 | $0.00160 |
Grade A, and why
gh-issues 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 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.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 1mo ago First seen · 212 lines · 46 tokens per session scan A c50fbec33b7b
gh-issues is a skill published in the GitHub repository anotherben/claude-harness (7 stars, last pushed 3mo ago), with no licence file. It adds 46 tokens to every session and 1,604 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-08-31.
Other skills, from other repositories
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
lerna
Best practices for Lerna monorepo management, versioning, and publishing.
yd-git-ship
A GitLab delivery workflow for coding agents. It defines how to create issues and branches, write commits, open and merge merge requests, and track continuous integration checks; continuous integration means automated checks run after changes are submitted.
ccc-triage
Triage a GitHub repo's open issues and PRs with the gh CLI: flag stale, unlabeled and CI-failing items, propose labels and next actions, apply labels one confirmed item at a time, or summarize the backlog. Use when a maintainer asks to triage issues or PRs, label the backlog, or wants a digest.
ccc-tasks
Track work in one markdown file, tasks/todo.md, with checkboxes, P0-P3 priorities and status marks; no database, service or sync. Use when the user asks for a todo list, wants to track personal or side-session tasks, or types $ccc-tasks.
hotfix
Single-issue workflow for quick fixes and small changes that don't need full epic tracking. Creates a branch, implements the fix, commits with issue tracking, and closes.