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 OpenScribbler/syllago --skill code-reviewgit clone --depth 1 https://github.com/OpenScribbler/syllagoWrote 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/openscribbler/syllago/code-review)<a href="https://agentmods.dev/skills/openscribbler/syllago/code-review"><img src="https://agentmods.dev/badge/skills/openscribbler/syllago/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/openscribbler/syllago/code-review"><img src="https://agentmods.dev/badge/skills/openscribbler/syllago/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.00005 | $0.00239 |
| Opus 5.5 | $0.00002 | $0.00096 |
| Sonnet 5.5 | $0.00001 | $0.00048 |
| Haiku 4.5 | $0.00001 | $0.00024 |
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
Perform a systematic code review across four dimensions:
Correctness
- Does the logic handle edge cases (empty input, boundary values, concurrent access)?
- Are error paths handled and propagated correctly?
- Do tests cover the happy path and at least one failure path?
- Does the implementation match the spec or PR description?
Clarity
- Are names accurate and self-documenting?
- Is each function focused on one responsibility?
- Would a new contributor understand this in 5 minutes without explanation?
Safety
- Are there injection risks at system boundaries (SQL, shell, HTML output)?
- Is untrusted input validated before use?
- Are secrets or credentials accidentally exposed in code or logs?
Completeness
- Are there missing test cases for documented behavior?
- Is documentation updated if behavior changed?
- Are breaking changes backwards-compatible or flagged?
Output format
Report findings as:
- Must Fix — correctness or security issues that block merge
- Should Fix — meaningful improvements worth addressing now
- Consider — observations that may improve the code but aren't blocking
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.
- 1mo ago First seen · 41 lines · 5 tokens per session scan A 882bb33d051e
code-review is a skill published in the GitHub repository OpenScribbler/syllago (15 stars, last pushed 3d ago), licensed Apache-2.0. It adds 5 tokens to every session and 239 once invoked, about $0.0000 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-30.
Other skills, from other repositories
code-review-go
Deep Go-specific code review covering goroutine lifecycle, data races, error wrapping, domain modeling, and interface design. Applied in addition to the generic code-review skill when Go code is detected. Invoked when reviewing Go PRs, Go code changes, or performing Go-specific quality checks.
crit-cli
Use when an agent needs to author or reply to crit inline comments programmatically (including multi-agent workflows commenting on shared code/plans/docs/proposals), publish or unpublish a crit review with crit share, sync a crit review to or from a GitHub PR or GitLab MR, or read/interpret a crit review JSON file.…
crit
Review code changes, a plan, a live page (running dev server), or a local HTML file with Crit inline comments and structured human feedback. Use only when the user explicitly invokes /crit or directly asks to use Crit; a generic review request does not count.
crit-story
Author a crit story and continue the interactive review loop only when the user explicitly invokes crit-story or directly asks you to generate a crit story. Do not infer this skill from generic review, PR, or diff-review requests.
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
design-review
Deep design review of Go codebase — naming, structure, consistency, interfaces, error handling. Scores each dimension and provides actionable fixes.