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/j-pster/psters_ai_workflow/requesting-code-reviewnpx skills add J-Pster/Psters_AI_Workflow --skill requesting-code-reviewgit clone --depth 1 https://github.com/J-Pster/Psters_AI_WorkflowWrote 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/j-pster/psters_ai_workflow/requesting-code-review)<a href="https://agentmods.dev/skills/j-pster/psters_ai_workflow/requesting-code-review"><img src="https://agentmods.dev/badge/skills/j-pster/psters_ai_workflow/requesting-code-review.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.00027 | $0.00139 |
| Opus 5 | $0.00014 | $0.00069 |
| Sonnet 5 | $0.00005 | $0.00028 |
| Haiku 4.5 | $0.00003 | $0.00014 |
Grade A, and why
requesting-code-review 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 6d 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.
What it actually says
Requesting Code Review
Use this skill when you want a consistent, high-signal review request.
How to use
- Define review scope:
- target diff/branch/PR
- changed file list
- Ask reviewer to use the template in
code-reviewer.md. - Require severity-labeled findings with concrete recommendations.
Output requirements
- Findings first, ordered by severity.
- Each finding includes impacted files/symbols.
- Keep summaries short; focus on risks and regressions.
What ships with it
1 file 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.
- 6d ago First seen · 23 lines · 27 tokens per session scan A 859754cc231d
requesting-code-review is a skill published in the GitHub repository J-Pster/Psters_AI_Workflow (290 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 139 once invoked, about $0.0001 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
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.
issue-progress-tracking
GitHub issue workflow ceremony using gh CLI — labels issues as in-progress, creates feature branches (issue/N-description), commits with issue references, posts progress comments, and links PRs with Closes #N. Keeps issues in sync with development work. Use when starting work on an issue, tracking progress, or…
ship-it
Code commit, PR creation, merge, and issue closure workflow via GitHub CLI (gh). Triggers after a goal (GitHub Issue) implementation is complete — commit code, push branch, create PR, merge, then close the issue. Use when the user says "提交代码", "commit and merge", "创建PR", "合入", "关闭issue", "ship-it", or when a goal…
git-workflow
Git operations: commits, branches, PRs, and conflict resolution.
git-expert
Expert-level Git version control with advanced workflows, branching strategies, and best practices for team collaboration. Use when the user mentions version control, collaboration, or workflow, or when the task involves Essential Git Commands, Advanced Git Techniques, Branching Strategies, or Conflict Resolution.
gza-task-improve
Address feedback for a gza task inline — reads review findings and/or unresolved comments, checks out the branch, fixes must-fix items and comments, runs verify, and commits.