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 agentry-ai/agentry --skill githubgit clone --depth 1 https://github.com/agentry-ai/agentryWrote 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/agentry-ai/agentry/github)<a href="https://agentmods.dev/skills/agentry-ai/agentry/github"><img src="https://agentmods.dev/badge/skills/agentry-ai/agentry/github/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/agentry-ai/agentry/github"><img src="https://agentmods.dev/badge/skills/agentry-ai/agentry/github.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.00000 | $0.00956 |
| Opus 5.5 | $0.00000 | $0.00382 |
| Sonnet 5.5 | $0.00000 | $0.00191 |
| Haiku 4.5 | $0.00000 | $0.00096 |
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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: GitHub (existing-repo workflow)
Use when the user names a GitHub repo to work on ("fix the bug in acme/widgets", "add tests to my-org/api", "open a PR against octocat/hello-world for the spelling issue").
Precondition: is GitHub bound?
Check the env array in the sandbox_create response (or the
sandbox env later). If GITHUB_TOKEN is present, GitHub is wired:
the gh CLI, git over HTTPS, and every GitHub SDK that respects
GITHUB_TOKEN will Just Work without further setup.
If GITHUB_TOKEN is NOT there, stop and tell the user:
GitHub isn't bound on this cluster yet. Run
agentry service bind githubfrom your CLI (you'll be prompted for a Personal Access Token), then ask me to retry.
Do NOT try to clone a repo without a token — the clone will work for public repos but every push will fail with a confusing 403, which is worse than a clean "not configured" message.
Workflow
1. command_run "gh repo clone OWNER/REPO /workspace/projects/REPO"
2. command_run "cd /workspace/projects/REPO && git config user.email [email protected] && git config user.name $GITHUB_USERNAME"
3. Detect the project kind from /workspace/projects/REPO contents:
- package.json with "next" dep → kind=nextjs
- package.json (any other) → kind=custom (read start_command from package.json scripts)
- app.py with `import streamlit` → kind=streamlit
- app.py with `from fastapi import` → kind=fastapi
- requirements.txt + no entry app → kind=python-script
- .html + assets only → kind=static-html
- else → kind=custom (ask user for start_command)
4. project_create name=REPO kind=<detected> — this writes
.sandbox-project.json without touching the cloned source.
5. project_start name=REPO and iterate normally.
project_create writes the manifest into the cloned dir without
clobbering existing files — its starter-file scaffolding only fills
in files that don't already exist, so a real repo just gets the
manifest layer.
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.
- 2mo ago First seen · 86 lines · 0 tokens per session scan A 9ae289c2f066
github is a skill published in the GitHub repository agentry-ai/agentry (6 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 956 tokens. 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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.