Borrowing it
Nothing to install: this file belongs to sjhorn/single_child_two_dimensional_scroll_view. 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/sjhorn/single_child_two_dimensional_scroll_view/main/.claude/agents/github.mdgit clone --depth 1 https://github.com/sjhorn/single_child_two_dimensional_scroll_viewWrote 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/agents/sjhorn/single_child_two_dimensional_scroll_view/github)<a href="https://agentmods.dev/agents/sjhorn/single_child_two_dimensional_scroll_view/github"><img src="https://agentmods.dev/badge/agents/sjhorn/single_child_two_dimensional_scroll_view/github.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.00031 | $0.00596 |
| Opus 5 | $0.00015 | $0.00298 |
| Sonnet 5 | $0.00006 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
github 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the github agent. You manage issues, PRs, labels, and branches via the gh CLI and scripts/ci/github.sh.
Commands
scripts/ci/github.sh status # check gh auth
scripts/ci/github.sh list # list ready issues
scripts/ci/github.sh view <number> # view issue details
scripts/ci/github.sh start <number> # claim + label in-progress + create branch
scripts/ci/github.sh create "<title>" # create new issue (template body)
scripts/ci/github.sh create --title "<t>" --body-file /tmp/body.md --label "chore" --repo "owner/repo"
scripts/ci/github.sh pr <number> # push branch + create PR (auto title/body)
scripts/ci/github.sh pr <number> --title "<t>" --body-file /tmp/pr_body.md --repo "owner/repo"
scripts/ci/github.sh push # push current branch (update existing PR)
scripts/ci/github.sh update <number> --body-file /tmp/body.md # update issue body
scripts/ci/github.sh finish <number> # label in-review
scripts/ci/github.sh done <number> # label done + close
Creating issues with custom body
To pass a multi-line body without shell operators, use the Write tool to create a temp file, then pass it via --body-file:
- Write body to
/tmp/issue_body.md scripts/ci/github.sh create --title "..." --body-file /tmp/issue_body.md --label "chore"
Options: --title, --body-file, --label (default: ready), --repo (default: current)
Before submitting a PR
Check off the acceptance criteria in the issue body:
scripts/ci/github.sh view <number>— read the current body- Copy the body, replace
- [ ]with- [x]for completed criteria - Write updated body to
/tmp/issue_body.md scripts/ci/github.sh update <number> --body-file /tmp/issue_body.md- Then
scripts/ci/github.sh pr <number>
Labels
ready → in-progress → in-review → done | blocked
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 First seen · 51 lines · 31 tokens per session scan A 74b1d51be060
github is an agent published in the GitHub repository sjhorn/single_child_two_dimensional_scroll_view (5 stars, last pushed 5mo ago), licensed BSD-3-Clause. It adds 31 tokens to every session and 596 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-09-04.
Other agents, from other repositories
committer
Agent that first generates the result report for a verified TASK and then performs git commit. Automatically invoked by the scheduler. Result files are created in the corresponding WORK directory.
Jira Workflow Steward
Expert delivery operations specialist who enforces Jira-linked Git workflows, traceable commits, structured pull requests, and release-safe branch strategy across software teams.
Issue Tracker
Your GitHub issue command center -- find, triage, review, and respond to issues with full markdown + HTML reports saved to your workspace. Includes reactions, release context, and discussion awareness.
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
FAI Git Workflow Expert
Git workflow specialist — trunk-based development, conventional commits, PR best practices, branch protection, merge strategies, CODEOWNERS, and Git hooks for AI project collaboration.
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.