Borrowing it
Nothing to install: this file belongs to 100yenadmin/boardstate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/100yenadmin/boardstate/main/.claude/skills/boardstate-dev/SKILL.mdgit clone --depth 1 https://github.com/100yenadmin/boardstateWrote 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/100yenadmin/boardstate/boardstate-dev)<a href="https://agentmods.dev/skills/100yenadmin/boardstate/boardstate-dev"><img src="https://agentmods.dev/badge/skills/100yenadmin/boardstate/boardstate-dev/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/100yenadmin/boardstate/boardstate-dev"><img src="https://agentmods.dev/badge/skills/100yenadmin/boardstate/boardstate-dev.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.00062 | $0.00940 |
| Opus 5.5 | $0.00025 | $0.00376 |
| Sonnet 5.5 | $0.00012 | $0.00188 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
boardstate-dev scanned grade A 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
version (registry curl, not `npm view` — this machine pins `min-release-age`). How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Boardstate development
Read AGENTS.md §5 first (layout, commands, read-first list). This skill adds the process that isn't obvious from the tree.
The loop
- Branch off
main(worktree for anything non-trivial). Never commit to main directly except docs-only follow-ups. - Scoped gates locally, full matrix in CI.
pnpm --filter @boardstate/<pkg> testfor what you touched + rootpnpm typecheck+pnpm lint(oxlint zero-warnings + prettier). Do not run the full suite locally — CI runs Node 22 + 24. - Changeset per behavior change (
.changeset/*.md, patch/minor per touched package). Docs/examples-only changes need none. - PR → CI green → merge. The changesets bot opens a Version Packages PR; merging it IS the release train (publishes all bumped packages with npm provenance). One train per batch — let related PRs ride together.
- After the train: verify
dist.attestationson the registry for each published version (registry curl, notnpm view— this machine pinsmin-release-age).
Verify discipline (this repo's record: 10 real defects caught this way)
Green tests prove the happy path; the seams need adversaries. Before merging anything touching grants, the pending-action engine, the sandbox, bindings, or the agent tools:
- Run an adversarial pass per named invariant (SPEC §11/§17/§18): one skeptic per invariant, prompted to REFUTE with concrete inputs and file:line citations.
- Gate every caller. A guarded mutation reachable via >1 path (RPC / agent tool /
import / CLI) is only as strong as its weakest caller — grep every call site; don't trust
the gate's own "holds for all callers" comment. (The agent
workspace.replaceself-grant bypass shipped exactly this way.) - Reads ≠ actions. A read path must never reuse a side-effecting verb. If a "read" can
park, queue, or mutate, it's the wrong verb (
dashboard.connector.readexists because a read binding routed throughaction.invokeparked mutations on every refresh). - Claim-before-await for single-shot actions (mark terminal synchronously before the
first
await) and compute-under-the-lock for read-modify-write unions (inside the store's mutate producer, never from an earlier unlocked read). - Functional ≠ visually correct. After UI-adjacent changes, look at the rendered board (preview server / demo), not just the render model — a missing stylesheet passes every test.
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.
- 2mo ago First seen · 65 lines · 62 tokens per session scan A 0db3816507a0
boardstate-dev is a skill published in the GitHub repository 100yenadmin/boardstate (24 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 940 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
ship
Pre-release gate. Run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog). Use before tagging a release.
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
ship-workflow
Resumable shipping lifecycle: reconciles current Git and GitHub facts from any entry (dirty default or feature branch, local commits, published branch, open PR, existing manual or native stack, merged work), commits dirty work as lossless logical commits, publishes or reuses the PR, requires current CI and review…
mathodology-dev-test-release
Use when checking skill metadata, references or repository boundaries, or preparing an explicitly requested skills release.