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 soden46/engineer-flow --skill version-control-reviewgit clone --depth 1 https://github.com/soden46/engineer-flowWrote 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/soden46/engineer-flow/version-control-review)<a href="https://agentmods.dev/skills/soden46/engineer-flow/version-control-review"><img src="https://agentmods.dev/badge/skills/soden46/engineer-flow/version-control-review/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/soden46/engineer-flow/version-control-review"><img src="https://agentmods.dev/badge/skills/soden46/engineer-flow/version-control-review.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.00027 | $0.00339 |
| Opus 5.5 | $0.00011 | $0.00136 |
| Sonnet 5.5 | $0.00005 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
version-control-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 1mo 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
version-control-review
Use this skill for code review, change inspection, commits, merges, branch workflows, and review preparation.
Code Review
Evaluate:
- correctness
- regressions
- security impact
- data integrity
- tests
- maintainability
- scope creep
Prioritize behavior-affecting problems over style preferences.
Review changed behavior in context, not only individual lines.
Changes
Keep commits coherent where practical.
Avoid mixing unrelated changes.
Before merging:
- ensure conflicts are resolved intentionally
- run relevant verification
- inspect unexpected generated or configuration changes
Do not rewrite shared history without understanding the collaboration impact.
Adaptation
Use project evidence to determine the actual language, framework, runtime, and existing conventions.
When stack-specific implementation guidance is needed, prefer project evidence, native framework or language mechanisms, and relevant user-installed specialist skills. Technology-specific guidance must not redefine or weaken the core engineering requirement.
Absorbed Legacy Capability: code-review
The following framework-agnostic knowledge was preserved from the previous Engineer Flow capability during consolidation.
Code Review
Prioritize findings over summaries.
- Look for bugs, regressions, security issues, and missing tests.
- Ground findings in files, commands, or observable behavior.
- Order issues by severity.
- State residual risk when checks are incomplete.
- Keep style-only comments secondary.
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.
- 1mo ago First seen · 65 lines · 27 tokens per session scan A f0c604888612
version-control-review is a skill published in the GitHub repository soden46/engineer-flow (3 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 339 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
code-review-loop
Use when opening a PR for review or when receiving review feedback. Activate for keywords like "code review", "PR review", "request review", "review feedback", "address comments", "reviewer said". Covers both ends of the loop: preparing a reviewable PR and acting on feedback rigorously. Always engage with every…
git-pr-workflows-git-workflow
Orchestrate a comprehensive git workflow from code review through PR creation, leveraging specialized agents for quality assurance, testing, and deployment readiness. This workflow implements modern g.
ticketcreate-pr
Create pull request with aggressive security and architecture review.
ticketreview-commit
Thorough code review, verify requirements met, commit with detailed message.
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.