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/julien777z/code-review-action/generic-pushnpx skills add julien777z/code-review-action --skill generic-pushgit clone --depth 1 https://github.com/julien777z/code-review-actionWrote 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/julien777z/code-review-action/generic-push)<a href="https://agentmods.dev/skills/julien777z/code-review-action/generic-push"><img src="https://agentmods.dev/badge/skills/julien777z/code-review-action/generic-push.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.00035 | $0.00343 |
| Opus 5 | $0.00017 | $0.00171 |
| Sonnet 5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
generic-push 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 5d 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.
This is a copy
100% identical to generic-push — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Generic Publishing Metadata
- Keep branch names, commit messages, pull request titles, and pull request bodies generic without requiring them to repeat one phrase.
- Choose independent wording for each artifact and commit so each message describes its change category without exposing domain names, sensitive identifiers, or repository-specific context.
Examples:
Fixes action button,Fixes UI issue, orUpdates tests. - Use the repository's required branch prefix with a slug derived from a generic description of the overall change.
Example:
agent/fixes-ui-bugs, whereagent/stands for the repository-required prefix. - Keep pull request titles concise, but allow pull request bodies to use longer paragraphs, bullets, and validation notes when every detail remains generic.
- Longer descriptions may explain behavior and causes with generic nouns such as
action,button,modal,request, orpage. - Prefer an informative generic description over a one-sentence body that omits distinct change categories or validation performed.
- Preserve an existing non-default branch when repository rules require it, while keeping new commit and pull request metadata generic.
- When multiple repositories are involved and this skill applies to any of them, keep every repository's publishing metadata independent and isolated.
- Never mention another involved repository, its branch, pull request, implementation, or coordination context in a repository's branch name, commit message, pull request title, pull request body, or other publishing metadata.
- Leave automation-owned branch and pull request metadata unchanged.
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.
- 5d ago First seen · 20 lines · 35 tokens per session scan A 0ba39e3ebb75
generic-push is a skill published in the GitHub repository julien777z/code-review-action (2 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 343 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to generic-push, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
crew-commit
Canonical commit workflow for Gas Town crew members: pre-flight checks, branch creation, gt commit with agent identity, push, and PR creation. Use when ready to commit and submit work for review.
cherry-pick
Cherry-pick a commit from main to a Sui release branch, create the release PR, and report the PR URL.
task-snapshot
Create a commit or tag snapshot only when explicitly requested for a milestone, reproducibility checkpoint, handoff, or pinned artifact.
mflux-pr
Make a clean PR in mflux (inspect diff, quick verification, commit, push, open PR) using repo conventions.
comet-safe-delivery
在保护无关脏改动、关联 worktree、子模块和用户明确边界的前提下，提交、推送、合并或完成范围明确的 Comet 变更。用户要求提交、推送、合并回目标分支、清理 worktree 或交付已准备好的改动时使用。.