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 izkreny/agentifico --skill review-textgit clone --depth 1 https://github.com/izkreny/agentificoWrote 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/izkreny/agentifico/review-text)<a href="https://agentmods.dev/skills/izkreny/agentifico/review-text"><img src="https://agentmods.dev/badge/skills/izkreny/agentifico/review-text/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/izkreny/agentifico/review-text"><img src="https://agentmods.dev/badge/skills/izkreny/agentifico/review-text.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.00059 | $0.00583 |
| Opus 5 | $0.00030 | $0.00292 |
| Sonnet 5 | $0.00012 | $0.00117 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
review-text 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 9d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review text
When to Use
- Check
selected textor awhole filefor spelling, grammar, punctuation, style, or clarity. - Review markdown, documentation, prompts, AGENTS.md files, comments, UI copy, emails, or commit messages.
- Tighten phrasing without changing meaning.
- Apply minimal wording fixes after the user asks to update the text.
Instructions
- Identify the request scope:
selected textwhole file
- Identify the request actions:
spelling and grammar issues: report only objective language issues.style and clarity feedback: report wording, structure, ambiguity, tone, and readability issues.apply fixes: update the text directly with the smallest effective edits.all: do all of the above actions
- Read the exact current text before making claims. Prefer the active selection or active file when available.
- Separate objective corrections from optional style suggestions.
- Preserve the author's intent, technical meaning, terminology, tone, and formatting.
- Be explicit about confidence.
- Say
no issues foundwhen none are present. - Mark subjective wording suggestions as optional.
- Say
- When rewriting text:
- Prefer the smallest edit that fixes the issue.
- Do not rewrite code, identifiers, or quoted literals unless explicitly requested.
- Keep markdown structure unchanged unless the structure itself is part of the problem.
- When editing workspace files, change only the relevant text and avoid unrelated rewrites.
Response Pattern
- For review-only requests:
- State whether any issues were found.
- List issues with short explanations and suggested wording.
- Include a cleaned-up snippet only when it adds value.
- For apply requests:
- Make the minimal edits directly.
- Summarize what changed.
- Mention any remaining optional style improvements separately.
Style Heuristics
- Prefer direct instructions over biography in agent and configuration files.
- Prefer operational verbs such as
apply,use,follow,load, andcheckin instruction files. - Remove filler phrases, duplicated words, and unnecessary commas.
- Keep parallel lists grammatically parallel.
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.
- 9d ago First seen · 63 lines · 59 tokens per session scan A 72fffc99bb4e
review-text is a skill published in the GitHub repository izkreny/agentifico (2 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 583 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…