A workflow for non-code repository changes such as documentation, configuration, continuous integration, or dependency updates. It uses separate Git branches and checks that the change stays within that scope.

Use it for docs, rules, configuration, CI, and dependency changes, including creating a branch, defining the scope, making the change, and verifying it.

It provides a fixed review path for small maintenance work and prevents application changes from being handled as simple chores.

chore — Skill for Claude Code by bjornjee/agent-dashboard

Install

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.

Any agent

npx skills add bjornjee/agent-dashboard --skill chore

Clone the repo

git clone --depth 1 https://github.com/bjornjee/agent-dashboard

Made for: Claude Code.

Or install agent-dashboard, the plugin that ships this one along with the rest of its 8 skills, 5 agents, 10 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bjornjee/agent-dashboard/chore/github.svg)](https://agentmods.dev/skills/bjornjee/agent-dashboard/chore)

Your own site

<a href="https://agentmods.dev/skills/bjornjee/agent-dashboard/chore"><img src="https://agentmods.dev/badge/skills/bjornjee/agent-dashboard/chore/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bjornjee/agent-dashboard/chore"><img src="https://agentmods.dev/badge/skills/bjornjee/agent-dashboard/chore.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 649 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00021	$0.00649
Opus 5.5	$0.00008	$0.00260
Sonnet 5.5	$0.00004	$0.00130
Haiku 4.5	$0.00002	$0.00065

Measured 1mo ago against content hash e93e29fe0e8a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

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.

adapters/claude-code/skills/chore/SKILL.md · 74 lines

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.
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:feature or /agent-dashboard:fix instead. If a rule or config change introduces new agent behavior, consider /agent-dashboard:feature for 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-fast when available.
- Agent workflow/rule changes that alter behavior: run the package test covering that workflow, or switch to /agent-dashboard:feature if 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:

Read the full file on GitHub · 74 lines

Changes

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 · 74 lines · 21 tokens per session scan A e93e29fe0e8a

Subscribe to this mod's changes

chore is a skill published in the GitHub repository bjornjee/agent-dashboard (26 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 649 once invoked, about $0.0001 per session on Opus 5.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.

Claude Code Git and workflow Writing and docs agent-orchestration ai-agents cli codex developer-tools

gh-find-prs

Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.

Hmbown/CodeWhale · 27 tokens

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.

Hmbown/CodeWhale · 57 tokens

chore