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 mhmdreza-rafiei/agent-tools --skill githubgit clone --depth 1 https://github.com/mhmdreza-rafiei/agent-toolsWrote 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/mhmdreza-rafiei/agent-tools/github)<a href="https://agentmods.dev/skills/mhmdreza-rafiei/agent-tools/github"><img src="https://agentmods.dev/badge/skills/mhmdreza-rafiei/agent-tools/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/mhmdreza-rafiei/agent-tools/github"><img src="https://agentmods.dev/badge/skills/mhmdreza-rafiei/agent-tools/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.00066 | $0.01369 |
| Opus 5 | $0.00033 | $0.00685 |
| Sonnet 5 | $0.00013 | $0.00274 |
| Haiku 4.5 | $0.00007 | $0.00137 |
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 8d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/github-setup
Make a GitHub repo recognizable and safe: security reporting, CI on
every push/PR, Dependabot, protected v* tags, a real GitHub Release
(not a folder named releases/), and community entry points. Match the
target repo's voice; default to this catalog's (plain English, no emoji,
Conventional Commits, no AI Co-authored-by).
When to use
New GitHub repo; "add security / quality / branches / rules / tags";
hardening agent-tools or a sibling repo (agentry); /github-setup.
Commands
/github-setup— apply the full checklist to the current repo./github-setup --dry-run— print the file list andghcalls; write nothing./github-setup --files-only— write in-repo files; skipghAPI (no auth).
Step 1 — Detect
- Remote:
owner/repo, default branch (mainunless the repo already uses another). - Kind: catalog (markdown/scripts, no app test suite) vs app (
package.jsonscripts). - Voice: README / AGENTS.md / LICENSE. Do not invent a credits section if the repo forbids it.
- Whether
ghis authenticated. If not, do files-only and print the API commands.
Step 2 — Community files (in the tree)
Write only what is missing or stale. Names are GitHub-mandated where noted.
| Path | Purpose |
|---|---|
SECURITY.md |
Private advisory reporting. No public issues for vulns. |
CONTRIBUTING.md |
Point at AGENTS.md / CI commands. Short. |
.github/CODEOWNERS |
* @<owner> |
.github/pull_request_template.md |
Conventional Commits, no secrets, how verified |
.github/ISSUE_TEMPLATE/config.yml |
Route security to advisories; optional Discussions |
.github/ISSUE_TEMPLATE/bug.yml |
Repro, expected, actual |
.github/DISCUSSION_TEMPLATE/q-and-a.yml |
Community Q&A when Discussions is on |
Skip CODE_OF_CONDUCT / FUNDING unless the target repo already has them.
SECURITY.md must name this repo's URL and scope (do not copy agentry's npm-package scope onto a catalog).
Step 3 — Quality CI + Dependabot
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.
- 8d ago First seen · 110 lines · 66 tokens per session scan A 36bdba41ec1e
github is a skill published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 24d ago), licensed MIT. It adds 66 tokens to every session and 1,369 once invoked, about $0.0003 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-03.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.