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 CodeInfinity1/Stram --skill code-reviewgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/code-review)<a href="https://agentmods.dev/skills/codeinfinity1/stram/code-review"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/code-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/codeinfinity1/stram/code-review"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/code-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.00032 | $0.00401 |
| Opus 5.5 | $0.00013 | $0.00160 |
| Sonnet 5.5 | $0.00006 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
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 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
Code Review
Purpose
Act as a reviewer, not a summarizer. Prioritize defects, behavioral regressions, security issues, missing tests, and risky assumptions.
When To Use
Use when the user asks for review, PR review, diff review, bug hunt, pre-merge check, or "is this safe".
Inputs And Evidence
- Git diff, changed files, tests, related docs, and intended behavior.
- Line references and execution path evidence.
Tool Map
run_shell_commandread_filesearch_workspacediff_rendertool_search
Workflow
- Inspect changed files and surrounding context.
- Understand intended behavior and affected execution paths.
- Look for concrete bugs before style concerns.
- Verify whether tests cover the changed behavior.
- Present findings first, ordered by severity, with file/line references.
- If no issues are found, state that clearly and note residual risk.
Native Implementation Boundaries
- Use Stram file/shell/diff tools.
- Do not import external reference GitHub code-review scripts.
- Do not use regex-only static checks as the review brain.
Safety And Approval
- Do not modify code during a pure review unless the user asks.
- Avoid exposing private code beyond the workspace.
- Keep comments actionable and grounded.
Verification
- Findings require specific evidence.
- Test gaps should name the missing behavior.
- Avoid speculative issues without a plausible failure mode.
Failure Modes
- Leading with a summary instead of defects.
- Reporting style nits while missing behavioral bugs.
- Reviewing only the diff and missing an affected caller.
References
- Shortlist item:
code-review. - Related user preference: review stance means findings first.
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 · 66 lines · 32 tokens per session scan A 737cdaadce2a
code-review is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 401 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-09-03.
Other skills, from other repositories
omh-verification-gate
This is an OMH verification-gate workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
omh-refactor-plan
This is an OMH refactor-plan workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
codex-adversarial-review
Use this skill to conduct aggressive, adversarial code reviews on git changes, branches, or PRs to detect critical edge cases, race conditions, security holes, and data loss risks. Triggers: user mentions "adversarial review", "break the code", "find vulnerabilities", "security audit PR", "race condition check", "ship…
generic-fullstack-code-reviewer
Review full-stack code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md compliance. Enforces TypeScript strict mode, input validation, GPU-accelerated animations, and design system consistency. Use when completing features, before commits, or reviewing pull requests.
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…