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 commands/sattyamjjain/proofloop/againstgit clone --depth 1 https://github.com/sattyamjjain/proofloopWhat 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.00014 | $0.00695 |
| Opus 5 | $0.00007 | $0.00347 |
| Sonnet 5 | $0.00003 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00069 |
Grade A, and why
against 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/against — Diff-Aware Score Delta
Renders a Unicode table comparing two scorecards for the same skill — per-dimension deltas plus a composite verdict (IMPROVED / REGRESSED / FLAT). Exits non-zero on composite regression so CI can gate on it.
Arguments
skill-name(required): Which skill's history to compare.--baseline-index N(optional, default-2): Index into the skill's scorecards sorted by timestamp ascending. Negative indices count from the end, so-2is the penultimate run (one before latest).--target-index N(optional, default-1): Same indexing as the baseline.-1is the latest run.
What to Do
-
Invoke the CLI:
python3 skills/judge/scripts/against.py \ --skill {skill-name} \ --scores-dir skills/judge/scores \ [--baseline-index N] [--target-index N] -
The script reads every
{skill-name}_*.jsonfile from the scores directory, sorts by timestamp, selects the two indices, and prints a delta table like:╭────────────────────────────╮ │ Proofloop delta: code-review │ ╰────────────────────────────╯ baseline: 2026-04-10T12:00:00Z composite 7.80/B target: 2026-04-18T12:00:00Z composite 8.60/A- dimension before after delta ───────────────────────────────────────────── correctness 8 9 +1.0 ↑ completeness 7 8 +1.0 ↑ adherence 8 9 +1.0 ↑ actionability 8 8 +0.0 → efficiency 7 8 +1.0 ↑ safety 10 10 +0.0 → consistency 5 8 +3.0 ↑ ───────────────────────────────────────────── composite 7.80 8.60 +0.80 ↑ Proofloop: IMPROVED (+0.80) -
Exit semantics:
- Exit 0 — improved or flat (≥ -0.05 composite delta).
- Exit 1 — fewer than 2 scorecards, or indices out of range.
- Exit 2 — regression (composite dropped > 0.05). CI gate.
Examples
/against code-review # penultimate vs. latest
/against code-review --baseline-index 0 # first-ever vs. latest
/against code-review --baseline-index -5 --target-index -1 # last 5 runs
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 · 74 lines · 14 tokens per session scan A aa751a9fc4b0
against is a command published in the GitHub repository sattyamjjain/proofloop (5 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 695 once invoked, about $0.0001 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 commands, from other repositories
test
Run Postman collection tests, analyze results, diagnose failures, and suggest fixes.
get-flow-run
Inspect a Postman Flow run by its Run ID — per-block logs, failing block, and status.
routine
Execute one maintenance routine defined in scv/routines/ .md (task + guardrails + exit-criteria contract), or list defined routines. SCV never schedules — pair with host features like /loop or cron yourself. Use whenever the user asks to run a recurring maintenance task, or asks what routines exist — not only when…
incident
Live incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep a UTC timeline. Use when production is broken RIGHT NOW; for the after-action write-up alone, use /orc:postmortem.
t800-onboard
Для чата с новичками. Показывает, что настроено в Cursor (global + local), и что умеет отдел T-800.
t800-bootstrap
Запускайте один раз при установке плагина или для новичка в чате.