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 skills/bjornjee/agent-dashboard/chorenpx skills add bjornjee/agent-dashboard --skill choregit 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/chore)<a href="https://agentmods.dev/skills/bjornjee/agent-dashboard/chore"><img src="https://agentmods.dev/badge/skills/bjornjee/agent-dashboard/chore.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 | $0.00021 | $0.00649 |
| Opus 5 | $0.00010 | $0.00324 |
| Sonnet 5 | $0.00004 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
chore 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 4d 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.
Make a non-code change.
Change description: $ARGUMENTS
Instructions
Follow these phases in order. Each phase has a gate — do not proceed until the gate is satisfied.
Phase 1: Branch Setup
- Derive a short kebab-case name from the change description.
- Switch to main:
git checkout main - Pull latest:
git pull origin main - Create a new branch from main:
git checkout -b chore/<name>- If the branch already exists, ask the user whether to resume it (
git checkout chore/<name>) or choose a new name.
- If the branch already exists, ask the user whether to resume it (
- Confirm the branch:
git branch --show-current
Gate: On the correct chore/<name> branch, based on latest main.
Phase 2: Scope
- Parse the change description — what needs to change and why?
- Identify the affected files.
- Confirm this is a non-code change (config, docs, rules, CI, dependencies). If it involves application logic or tests, suggest
/agent-dashboard:featureor/agent-dashboard:fixinstead. If a rule or config change introduces new agent behavior, consider/agent-dashboard:featurefor planning and review.
Gate: The scope is clear and limited to non-code changes.
Phase 3: Implement
- Make the changes.
- Run the smallest relevant verification:
- Docs/rules/config text only: run no test, or a docs/config validation command if the repo has one.
- Dependency, CI, Makefile, formatter, or test-runner changes: run the affected native command and full
make test/make test-fastwhen available. - Agent workflow/rule changes that alter behavior: run the package test covering that workflow, or switch to
/agent-dashboard:featureif implementation-level validation is needed.
Gate: Changes are applied. The relevant verification is complete and named.
Phase 4: Review
Review all changes for correctness and convention adherence. Apply all project rules and conventions that are in your context.
Gate: No issues remain.
Phase 5: Commit and Open PR
- Commit with a conventional commit message. Use the appropriate type:
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.
- 4d ago First seen · 74 lines · 21 tokens per session scan A e93e29fe0e8a
chore is a skill published in the GitHub repository bjornjee/agent-dashboard (21 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 649 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-30.
Other skills, from other repositories
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
local-frontend-check
Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.
ppt-review
Read this skill only after current officereview structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.
helmor-debug-operate
Operate, reproduce, and debug a running local Helmor desktop development build through the Tauri MCP bridge. Use when the user asks to use Tauri MCP, towery MCP, the local dev build, the Tauri webview, visual end-to-end validation, UI automation, screenshots, DOM/accessibility snapshots, IPC or log tracing…
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.