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 bjornjee/agent-dashboard --skill prgit clone --depth 1 https://github.com/bjornjee/agent-dashboardWrote 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/bjornjee/agent-dashboard/pr)<a href="https://agentmods.dev/skills/bjornjee/agent-dashboard/pr"><img src="https://agentmods.dev/badge/skills/bjornjee/agent-dashboard/pr/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/bjornjee/agent-dashboard/pr"><img src="https://agentmods.dev/badge/skills/bjornjee/agent-dashboard/pr.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.00014 | $0.02230 |
| Opus 5.5 | $0.00006 | $0.00892 |
| Sonnet 5.5 | $0.00003 | $0.00446 |
| Haiku 4.5 | $0.00001 | $0.00223 |
Grade C, and why
pr scanned grade C 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 1mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
`rm -rf <path>`. Run from the repo root. Never pass `/`, `~`, `.`, `..`, How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open a pull request for the current branch. This is the only sanctioned path
to PR creation — a pr-skill-gate hook blocks any direct gh pr create that
doesn't carry this skill's bypass marker.
Optional arguments: $ARGUMENTS
Instructions
Each phase has a gate. Do not proceed until it passes.
Phase 1: Sync state
Run in parallel:
git status— warn if uncommitted changes (but proceed; the cleanup phase may add commits anyway).BASE=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's|refs/remotes/origin/||' || echo main)— detect default branch.git branch --show-current— current branch.git rev-parse --abbrev-ref @{upstream} 2>/dev/null— does it track a remote?git log --oneline $(git merge-base HEAD "$BASE")..HEAD— commits on this branch.git diff --name-only "$BASE"...HEAD— files changed vs base. Save this list — it's the input to Phase 3.
Gate: You have the changed-file list and the base branch.
Phase 2: Clean up scratch artifacts
Delete transient files left over from implementation, testing, and discovery — screenshots, Playwright MCP output, and tmp scratch — before the cleanup pass inspects the diff. Untracked only. Never touch tracked or staged files.
-
Identify untracked artifacts. Use
git ls-files --others --exclude-standardfor unignored untracked files, andgit ls-files --others --ignored --exclude-standardfor ignored untracked files. Filter for these patterns:*.pngat the repo root only — these are typically Playwright/visual-audit screenshots. PNGs inside subdirectories (build outputsout/,dist/,build/, asset dirspublic/,static/, source dirssrc/, etc.) are legitimate and must NOT be deleted..playwright-mcp/(directory)*.tmp(anywhere)tmp/(directory, when at repo root or inside a subproject root)
-
If the list is empty, skip the rest of this phase.
-
Confirmation gate — deletion is destructive and irreversible. Show the user the exact list of paths about to be deleted (one line each) and ask explicit permission before deleting. If the user declines, skip deletion and proceed to Phase 3.
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.
- 1mo ago First seen · 168 lines · 14 tokens per session scan C 6bbb10afca37
pr is a skill published in the GitHub repository bjornjee/agent-dashboard (26 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 2,230 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-close-issues
Close resolved Codewhale issues only after verifying the landed commit/behavior, with a positive crediting comment; never from title alone.
gh-credit-harvest
Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.