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 pledgeandgrow/pledge-skills --skill ruffgit clone --depth 1 https://github.com/pledgeandgrow/pledge-skillsWrote 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/pledgeandgrow/pledge-skills/ruff)<a href="https://agentmods.dev/skills/pledgeandgrow/pledge-skills/ruff"><img src="https://agentmods.dev/badge/skills/pledgeandgrow/pledge-skills/ruff/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/pledgeandgrow/pledge-skills/ruff"><img src="https://agentmods.dev/badge/skills/pledgeandgrow/pledge-skills/ruff.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.00031 | $0.01677 |
| Opus 5 | $0.00015 | $0.00839 |
| Sonnet 5 | $0.00006 | $0.00335 |
| Haiku 4.5 | $0.00003 | $0.00168 |
Grade C, and why
ruff-docs scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -LsSf https://astral.sh/ruff/install.sh | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -LsSf https://astral.sh/ruff/install.sh | sh How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ruff — Extremely Fast Python Linter & Formatter
Overview
Ruff is an extremely fast Python linter and code formatter written in Rust. It is designed as a drop-in replacement for Flake8, isort, Black, and many Flake8 plugins — all reimplemented in Rust as first-party features. Ruff supports Python 3.7 through 3.14, ships with 900+ built-in rules, includes an automatic fix mode, built-in caching, Jupyter Notebook support, and a built-in language server for editor integration.
Key Features
- Speed: 10–100x faster than Flake8 and comparable linters, written in Rust.
- Unified toolchain: Linter, formatter, import sorter, and language server in a single binary.
- 900+ rules: Re-implementations of popular Flake8 plugins (flake8-bugbear, flake8-comprehensions, flake8-simplify, pydocstyle, isort, pyupgrade, and many more).
- Formatter: Drop-in replacement for Black with configurable quote style, indent style, line endings, and docstring code formatting.
- Automatic fixes: Many rules are auto-fixable via
--fix; unsafe fixes available via--unsafe-fixes. - Configuration: Supports
pyproject.toml,ruff.toml, and.ruff.tomlwith hierarchical discovery and config inheritance viaextend. - Jupyter Notebooks: Built-in linting and formatting of
.ipynbfiles (v0.6.0+). - Editor integrations: Built-in language server (
ruff server), VS Code extension, Neovim, Vim, Helix, Emacs, PyCharm, Sublime Text, Zed, and more. - Preview mode: Opt-in to unstable rules and formatting styles before they become stable.
- Shell autocompletion: bash, zsh, fish, elvish, powershell, fig.
- No Rust required: Ships as a standalone binary; installable via
uv,pip,pipx, or standalone installers.
Skill File Structure
| File | Contents |
|---|---|
SKILL.md |
This file — overview, quick reference, feature summary |
getting-started.md |
Installation, first run, basic configuration, project setup |
api.md |
Full reference: CLI commands, configuration options, rules by category, linters, settings |
guides.md |
Editor setup, CI/CD integration, migration from Flake8/Black/isort, best practices, FAQ |
What ships with it
3 files 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.
- 9d ago First seen · 170 lines · 31 tokens per session scan C 4ec7c55b14c0
ruff-docs is a skill published in the GitHub repository pledgeandgrow/pledge-skills (10 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 1,677 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
truecourse-analyze
Run TrueCourse architecture analysis on this repository.
megalinter-check
Collect MegaLinter lint errors for the current repository. Use when the user wants to know if the code passes linting, why the MegaLinter CI job fails, or before/after fixing lint errors. Two modes - watch a CI job (GitHub Actions, GitLab CI, Azure Pipelines, Bitbucket Pipelines) and parse its logs, or run MegaLinter…
megalinter-setup
Install or upgrade MegaLinter on a repository. Use when the user wants to add MegaLinter to a project, set up linting CI, update MegaLinter configuration or version, or says "install megalinter", "setup linting", "add code quality checks", "update megalinter skills". Always goes through npx mega-linter-runner…
argot-setup
Set argot up for a repository end to end — audit its history, decide what should shape its voice, fit, verify the fit actually catches things, tune the rules its own history says are noisy, and wire the places it runs (pre-write hook, pre-commit, MCP, CI). One sitting, one decision at a time, each proposed with the…
megalinter-fix
Fix the errors reported by MegaLinter. Use after megalinter-check found errors, or when the user pastes MegaLinter/CI lint errors and wants them fixed. Applies safe fixes automatically (auto-fix linters first, then guided manual fixes using per-linter fix guides), asks the user when fixing is ambiguous, and can…
argot-check
Score your working changes with argot — flag code foreign to this repo's own patterns (unfamiliar dependencies, APIs, constructs), functions the repo already has, code filed in the wrong place, imports that break the repo's layering, and tests weakened, disabled, or deleted alongside a production change — before…