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/scorecardgit 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.00010 | $0.00616 |
| Opus 5 | $0.00005 | $0.00308 |
| Sonnet 5 | $0.00002 | $0.00123 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade A, and why
scorecard 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/scorecard — Score History & Trends
Display historical scores for skills that have been evaluated by Proofloop.
Arguments
skill-name(optional): Filter to a specific skill. If omitted, show all skills.--last N(optional): Show only the last N evaluations. Default: 10.--all(optional): Show all evaluations regardless of limit.
What to Do
- Read score files from
skills/judge/scores/directory - Parse each JSON score file
- Filter by skill name if provided
- Sort by timestamp (newest first)
- Limit to last N if specified
- Display formatted table:
┌─────────────────────────────────────────────────────────────┐
│ PROOFLOOP SCORE HISTORY │
├──────────────┬───────┬───────┬────────────┬────────────────┤
│ Skill │ Score │ Grade │ Date │ Trend │
├──────────────┼───────┼───────┼────────────┼────────────────┤
│ code-review │ 8.2 │ B+ │ 2026-02-13 │ ↑ (+0.4) │
│ code-review │ 7.8 │ B │ 2026-02-12 │ → (+0.0) │
│ security-scan│ 9.1 │ A │ 2026-02-13 │ ↑ (+0.6) │
├──────────────┼───────┼───────┼────────────┼────────────────┤
│ AVERAGES │ 8.37 │ B+ │ │ │
└──────────────┴───────┴───────┴────────────┴────────────────┘
-
Calculate trends:
- Compare each score to the previous score for the same skill
- ↑ = improved by 0.3+
- ↓ = declined by 0.3+
- → = stable (within 0.3)
-
Show averages per skill and overall
If no scores exist yet, inform the user: "No scores found. Run /judge after a skill execution to start building history."
Related commands
/against— side-by-side delta between two specific runs of the same skill./benchmark— delta between a skill's historical average and the reference standards inskills/judge/references/benchmark-standards.md.python3 skills/judge/scripts/studio.py --scores-dir skills/judge/scores --output proofloop-studio.html— self-contained HTML dashboard with per-skill radar charts.
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 · 56 lines · 10 tokens per session scan A 03df7ac6f29f
scorecard is a command published in the GitHub repository sattyamjjain/proofloop (5 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 616 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
Запускайте один раз при установке плагина или для новичка в чате.