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.
git clone --depth 1 https://github.com/mse-online/farley_score_pluginWrote 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/commands/mse-online/farley_score_plugin/farley-score)<a href="https://agentmods.dev/commands/mse-online/farley_score_plugin/farley-score"><img src="https://agentmods.dev/badge/commands/mse-online/farley_score_plugin/farley-score.svg" alt="Measured on agentmods" 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.00015 | $0.05384 |
| Opus 5 | $0.00008 | $0.02692 |
| Sonnet 5 | $0.00003 | $0.01077 |
| Haiku 4.5 | $0.00002 | $0.00538 |
Grade B, and why
farley-score scanned grade B with 1 finding 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 7d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
1. Run: `PLUGIN_DIR=$(find ~/.claude/plugins -name "cli_calculator.py" 2>/dev/null | head -1 | sed 's|/lib/cli_calculator.py||')` -- this finds the plugin's root directory. How it starts
The opening of the file, as written. The whole thing — 444 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ENTRY POINT: Determine User Intent
CRITICAL: BEFORE doing anything else, determine how the user invoked this command.
If invoked WITH a target path
If the user's message includes a file path, directory path, or specifies what to analyse (e.g., /msec:farley-score tests/, /msec:farley-score src/test/java/, /msec:farley-score evaluate test quality for the whole project), skip the welcome menu and go directly to the 4-Phase Workflow section below.
If invoked WITHOUT a target path
If the user simply typed /msec:farley-score with no additional arguments or context, present the welcome menu.
Use the AskUserQuestion tool to present the menu. Do NOT output the options as plain text. This ensures the user gets a navigable interactive menu (arrow keys + Enter) rather than having to type a number.
Question: "Welcome to Farley Score! What would you like to do?" Header: "Farley Score"
Options (use these exact labels and descriptions):
- Label: "What is this?" -- Description: "Learn what the Farley Score tool does and how it works"
- Label: "Show me a demo" -- Description: "See a complete sample report instantly from bundled example tests"
- Label: "Analyse my tests" -- Description: "Run a full test quality analysis on your project"
- Label: "Coach me" -- Description: "Switch to interactive coaching mode with Socratic questioning"
Option 1: What is this?
Present this overview to the user:
Farley Score measures test quality, not just test coverage.
It evaluates your tests against Dave Farley's 8 Properties of Good Tests -- Understandable, Maintainable, Repeatable, Atomic, Necessary, Granular, Fast, and First (TDD) -- and produces a single number: the Farley Index (0-10).
The tool reads your test code (it never modifies anything), detects quality signals and anti-patterns, scores each property on a 0-10 scale, and produces a detailed report with evidence, worst offenders, and prioritised recommendations.
Not all properties are equal. Understandable and Maintainable have the highest weight (1.5x) because tests that read like specifications and survive refactoring deliver the most long-term value. Fast has the lowest weight (0.75x) because a slow but well-designed test beats a fast but poorly designed one.
A typical analysis takes 3-5 minutes depending on the size of your test suite.
Rating scale: Exemplary (9-10), Excellent (7.5-8.9), Good (6-7.4), Fair (4.5-5.9), Poor (3-4.4), Critical (0-2.9)
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.
- 7d ago First seen · 444 lines · 15 tokens per session scan B b79a754ce689
farley-score is a command published in the GitHub repository mse-online/farley_score_plugin (27 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 5,384 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.