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/devoxx/devoxxgenieideaplugin/reviewnpx skills add devoxx/DevoxxGenieIDEAPlugin --skill reviewgit clone --depth 1 https://github.com/devoxx/DevoxxGenieIDEAPluginWhat 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 | $0.00090 | $0.00542 |
| Opus 5 | $0.00045 | $0.00271 |
| Sonnet 5 | $0.00018 | $0.00108 |
| Haiku 4.5 | $0.00009 | $0.00054 |
Grade A, and why
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review
Overview
Review the current local changes or the implementation tied to a backlog task id and report concrete findings, not a changelog. Treat this as a code review unless the user explicitly asks for edits.
Workflow
-
Resolve the review target. If the prompt includes a backlog task id, locate the task markdown in
backlog/tasks/first, thenbacklog/completed/if needed. Read the description, acceptance criteria, and referenced files. If no task id is given, start fromgit status --shortand review the current local changes directly. -
Build review scope from local context. Check
git status --short, inspect the diff for files related to the task, and read surrounding code where behavior is affected. Preferrgand targetedgit diff -- <path>over broad scans. -
Review for defects and regressions. Prioritize:
- broken behavior versus the task intent
- stale callers or UI paths left behind after refactors
- contract mismatches across main/preload/renderer/shared code
- silent failure handling and misleading fallback behavior
- missing or weak tests for the changed behavior
- unnecessary performance regressions or duplicate work
- Verify when useful. Run focused tests for the touched area if they are available and cheap. Mention clearly when verification is blocked or when broader typecheck/test failures are unrelated.
Output
Report findings first, ordered by severity. For each finding:
- state the severity
- describe the bug/risk or improvement
- include clickable file references with line numbers when available
- explain the user-visible or maintenance impact briefly
After findings, include:
- open questions or assumptions if any
- a brief note on verification performed
If no findings are discovered, say that explicitly and mention residual risk or missing coverage.
Prompt Shape
Interpret prompts like review, review current changes, or review the changes from git status as a request to review the current working tree. Interpret prompts like task-56, review task-56, or review task-56 and report any issues/bugs or possible improvements as a review of the local changes associated with that task.
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.
- 2d ago First seen · 49 lines · 90 tokens per session scan A 7bbb2b8622d2
review is a skill published in the GitHub repository devoxx/DevoxxGenieIDEAPlugin (677 stars, last pushed 6d ago), licensed MIT. It adds 90 tokens to every session and 542 once invoked, about $0.0005 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
carta-consolidating-pnl
Consolidating P&L (Income Statement) across the entities of a firm, for any period the user picks — a month, quarter, year, or start-to-end date range. Produces TWO Excel tabs: detail P&L (Period + YTD Actual/Budget/Variance/%) and executive Summary P&L formula-linked to detail. Optional tag-view breaks Actuals down…
carta-compensation-benchmarks
Retrieves Carta Total Compensation market benchmarks (salary, equity, total cash) for a role. Output to chat or CSV. Market benchmarks are triggered by queries like: "sales benchmarks", "comp benchmarks", "market rate", "what does a [role] pay", "put benchmarks in a CSV", "get benchmarks", "get carta's market…
carta-compensation-scorecard
Carta Total Compensation scorecard — shows how a corporation's employees compare to market. Two lenses: corporation-level rollup (band distribution — what % of employees are below / at / above market) and per-employee scorecard (each employee's compa-ratio + percentile + market band). Triggered by queries like…
carta-issuance
Issue securities on a Carta cap table. Use when the user asks to issue certificates, stock certificates, option grants (ISO, NSO, EMI, CSOP, Unapproved, Startup Concessions, Non-Concessional, ZEPO), to draft shares or grants, or to resume issuing from a draft set. USE WHEN the user says "issue", "grant", "draft"…
carta-reporting
Default skill for all cap table data-display queries — use this whenever the user wants to see, list, or explore equity data for a single company. Covers grants, vesting schedules, stakeholders, securities, SAFEs, convertible notes, round history, preferred holders, liquidation seniority, and rights & preferences.…
carta-compensation-rolematcher
Classify a job title or description into the CTC taxonomy (job area, focus, level, track). Use when the user wants to know how a role is categorized or mapped to the taxonomy structure — not to fetch salary, equity, or benchmark numbers. Do NOT use when the user is asking for "market rates", "benchmark data"…