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/fledgeling-co/fledgeling-pluginsWrote 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/plugins/fledgeling-co/fledgeling-plugins/reckon)<a href="https://agentmods.dev/plugins/fledgeling-co/fledgeling-plugins/reckon"><img src="https://agentmods.dev/badge/plugins/fledgeling-co/fledgeling-plugins/reckon/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/plugins/fledgeling-co/fledgeling-plugins/reckon"><img src="https://agentmods.dev/badge/plugins/fledgeling-co/fledgeling-plugins/reckon.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
reckon 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 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.
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 — 10 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "reckon",
"description": "Work out what actually remains in a project by reconciling what it promised against what anybody proved — the feature briefs and PRD in docs/features-to-triage on one side, a test-campaign:test-campaign registry of cases, requirements, surfaces and defects on the other — and resolve every item on both sides into exactly one class of a total partition, so nothing can quietly fall out of the list. The classes carry different fix-shapes and different owners: named-but-unbuilt, named-but-unjoinable, measured-and-broken, never-measured, never-named, disputed, already-done-so-retire-it, and deliberately-waived. The one that matters most is never-measured, because a blocked or inconclusive check is not a pass and not a failure, and a remaining-work list that silently drops it reports a partial campaign as a finished product. That class is scheduled as the blockers behind it rather than case by case, each with the coverage it returns, because twenty blocked cases are usually three causes. Publishes a denominator per axis and never one blended percent, marks every figure as a floor, refuses to retire stated intent on weak-oracle or guessed evidence, refuses to let a requirement leave never-measured on its own evidence word when no passing case cites it, keeps waivers visible as exceptions rather than folding them into done, and gates the whole ledger with an exit code so a report that lost an item cannot pass. Then schedules what remains: ship-fleet:ship-fleet's wave model over the ledger, so items whose dependencies are met run in parallel, with sub-tasks nested under the item that cites them and a wall-clock range per item and per wave drawn from 1,842 measured Opus 4.8 and Opus 5 agent runs — always a range and never a number, because the measured p90 is over three times the median, and never a schedule implying a speedup better than the 4.0x ever observed. Emits three artifacts from one gated ledger: ledger.json, a comprehensive teWhat it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 579 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 Changed 5fd38a25e87d
- 10d ago First seen · 10 lines scan A e25eabff5bb7
reckon is a plugin published in the GitHub repository fledgeling-co/fledgeling-plugins (2 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-04.
Other plugins, from other repositories
load-tester
Load and stress testing for APIs and web services.
kit
Spec-driven Claude Code workflow with verification pipeline. Hooks, slash commands, and verification subagents.
looptimal
Turns an objective into a delivered, VERIFIED OUTCOME: frames a hash-pinned sealed acceptance suite, designs the right loop (the loop-design wizard, formerly LoopPrint), war-games it forward, executes with dynamic domain-expert sub-agents (maker != checker), and gates completion on a separate verifier re-running the…
headless
Headless browser automation for site comparison, E2E testing, and anti-bot-aware web research.
pict-test-designer
Design comprehensive test cases using PICT (Pairwise Independent Combinatorial Testing) for any piece of requirements or code. Analyzes inputs, generates PICT models with parameters, values, and constraints for valid scenarios using pairwise testing. Outputs the PICT model, markdown table of test cases, and expected…
local-test-plugin
Symlink-based local plugin testing for development workflow.