Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jaroslavsoucek-art/Giovanni/plugin install giovanniWrote 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/jaroslavsoucek-art/giovanni/redline)<a href="https://agentmods.dev/skills/jaroslavsoucek-art/giovanni/redline"><img src="https://agentmods.dev/badge/skills/jaroslavsoucek-art/giovanni/redline/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/jaroslavsoucek-art/giovanni/redline"><img src="https://agentmods.dev/badge/skills/jaroslavsoucek-art/giovanni/redline.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.00039 | $0.01486 |
| Opus 5.5 | $0.00016 | $0.00594 |
| Sonnet 5.5 | $0.00008 | $0.00297 |
| Haiku 4.5 | $0.00004 | $0.00149 |
Grade A, and why
redline 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/giovanni:redline
Run adversarial review on a draft with emphasis on the verbatim-strike list (lines, phrases, and sentences the principal should delete or replace). This command is an alias for /giovanni:review — same agent (giovanni:adversarial-reviewer), same verdict enum, same protocol — with a prompt parameter that biases the agent's output toward maximal line-level redlines.
Use /giovanni:redline instead of /giovanni:review when:
- The draft is ready in shape but needs surgical cuts before sending
- The principal already has the position locked and wants pure strike output, not strategic pushback
- Cosmetic / RLHF-stylism cleanup is the goal (the agent flags those as a verbatim strike list)
Use /giovanni:review (not /giovanni:redline) when:
- The position itself may be wrong (strategic pushback is the point)
- The draft is early-stage and needs counter-case construction, not line edits
The two commands return the same verdict format. The difference is emphasis: /giovanni:redline weights Pass 3 (symmetry/padding/RLHF-stylisms) and the verbatim-strike section higher than the strongest-counter-case section. Both still run all four passes.
Usage
/giovanni:redline <draft-path> # required positional
/giovanni:redline <draft-path> --position "..." # optional one-line position statement
/giovanni:redline <draft-path> --audience external # internal | external | mixed
If <draft-path> is omitted, the orchestrator looks for the draft inline in the message.
Argument syntax
Identical to /giovanni:review:
| Arg | Type | Default | Meaning |
|---|---|---|---|
<draft-path> |
positional | — | Relative path to draft file. |
--position "<text>" |
parameterized string | derived | One-line position statement. |
--audience <level> |
parameterized | inferred | internal / external / mixed. |
Pre-flight (binding — STOP on failure)
Identical to /giovanni:review. See ${CLAUDE_PLUGIN_ROOT}/skills/review/SKILL.md § Pre-flight.
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.
- today First seen · 112 lines · 39 tokens per session scan A 93d9a9878a40
redline is a skill published in the GitHub repository jaroslavsoucek-art/Giovanni (2 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 1,486 once invoked, about $0.0002 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-10-17.
Other skills, from other repositories
code-review
Perform thorough code reviews, identify bugs, suggest improvements, and explain code quality issues. Use when the user shares code and asks for a review, bug hunt, or quality feedback.
Simplify
Review code in the current working tree across three independent dimensions (reuse, quality, efficiency) and synthesise a small punch-list of high-value cleanups.
github-code-review
Comprehensive GitHub code review with AI-powered swarm coordination.
Pair Programming
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…
multi-reviewer-patterns
Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results.
code-review-excellence
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.