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 agentmods add skills/gxdevs/grouter/contributenpx skills add GXDEVS/grouter --skill contributegit clone --depth 1 https://github.com/GXDEVS/grouterWrote 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/gxdevs/grouter/contribute)<a href="https://agentmods.dev/skills/gxdevs/grouter/contribute"><img src="https://agentmods.dev/badge/skills/gxdevs/grouter/contribute.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 | $0.00135 | $0.02919 |
| Opus 5 | $0.00068 | $0.01460 |
| Sonnet 5 | $0.00027 | $0.00584 |
| Haiku 4.5 | $0.00014 | $0.00292 |
Grade A, and why
contribute 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 4d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
grouter — Contribution Flow
End-to-end helper for contributing to grouter (GXDEVS/grouter). Take the user from "I have changes" to "PR open on GitHub" with zero guesswork.
Ground rules — non-negotiable
- Use the developer's git identity. Read
git config user.nameandgit config user.email. Never rungit config --global user.*or override the identity. If unset, stop and tell the user to configure it (see step 0). - No emojis. Not in branch names, commit messages, PR titles, PR bodies, or terminal output. None.
- No Claude attribution. Do not append
Co-Authored-By: Claude …, "Generated with Claude Code", or any similar footer to commits or PRs. Leave the message ending with the body/footer the user approved. - Never force-push, never
--no-verify, never amend a commit that was already pushed. If a hook fails, fix the underlying issue and create a new commit. - Commit scope matches the user's intent. Ask per logical change — one feature/fix per commit. Do not silently bundle unrelated files.
- Confirm before destructive or shared-state actions. Branch deletion, rebases, PR creation, and
git pushalways get an explicit "yes" from the user.
Step 0 — Verify the developer is logged in
Run these checks in parallel before anything else:
git config user.name
git config user.email
git -C . remote get-url origin
gh auth status 2>&1 || true
Decision table:
| Check | Missing → do this |
|---|---|
user.name / user.email empty |
Stop. Tell the user to run git config --global user.name "Your Name" and git config --global user.email "[email protected]" themselves, then retry. |
gh auth status not logged in |
Tell the user to run gh auth login in the prompt as ! gh auth login (interactive). PR step needs it. Commits/branch work can still proceed. |
origin points to a fork |
Fine — PRs will target GXDEVS/grouter:main via gh pr create --repo GXDEVS/grouter. Confirm the fork URL with the user. |
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.
- 4d ago First seen · 259 lines · 0 tokens per session scan A cc0182a4780d
contribute is a skill published in the GitHub repository GXDEVS/grouter (55 stars, last pushed 6d ago), licensed MIT. It adds 135 tokens to every session and 2,919 once invoked, about $0.0007 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-08-30.
Other skills, from other repositories
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
document
Run /document pr | changelog | release-note | postmortem (or let it ask) to write the human facing prose about a change. Drafts from the real commits and diff, writing to the right place. Does not write code, tests, or specs.
git-push
把项目推送到 GitHub，三种模式自动判断：首次推送（大文件扫描 → 生成 .gitignore → git init → gh 建仓 → 推送）、日常更新（commit + push）、版本发布（打 tag + 建 Release，可附下载文件）。核心原则是安全第一：推之前必扫大文件和敏感文件，宁可多问一句也不把不该推的东西推上去。当用户说"推到GitHub""推送到GitHub""git push""上传到GitHub""提交并推送""发版本""打release""打tag""/git-push"时触发。不适用于：规划哪些功能进哪个版本号（用 issue-pool——本 skill 只负责把已经定好的版本号打成…
ship
Commit, push, and create a PR for staged changes, with confirmation at each step. Use when your work is done and you want to ship.
git-workflow
Git operations: commits, branches, PRs, and conflict resolution.
conventional-commits
Conventional Commits specification for consistent, machine-readable git commit messages. Use when crafting commit messages, enforcing commitlint rules, or generating changelogs/releases.