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 oikon48/claudecode-book --skill taskboard-feature-devgit clone --depth 1 https://github.com/oikon48/claudecode-bookWrote 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/oikon48/claudecode-book/taskboard-feature-dev)<a href="https://agentmods.dev/skills/oikon48/claudecode-book/taskboard-feature-dev"><img src="https://agentmods.dev/badge/skills/oikon48/claudecode-book/taskboard-feature-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/oikon48/claudecode-book/taskboard-feature-dev"><img src="https://agentmods.dev/badge/skills/oikon48/claudecode-book/taskboard-feature-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.00067 | $0.00202 |
| Opus 5.5 | $0.00027 | $0.00081 |
| Sonnet 5.5 | $0.00013 | $0.00040 |
| Haiku 4.5 | $0.00007 | $0.00020 |
Grade A, and why
taskboard-feature-dev 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.
What it actually says
TaskBoardに機能を追加するときは、以下の順で進めてください。
- 追加する機能のユーザー操作を確認する
- 失敗するテストを先に追加する
useTaskBoardに状態管理を集約する- 既存コンポーネントの責務分担を変えずにUIを更新する
npm run test:runとnpm run buildで検証する- 必要に応じてPlaywright MCPで画面操作を確認する
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 · 14 lines · 67 tokens per session scan A 0db2232039f2
taskboard-feature-dev is a skill published in the GitHub repository oikon48/claudecode-book (23 stars, last pushed 2mo ago), licensed MIT. It adds 67 tokens to every session and 202 once invoked, about $0.0003 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-31.
Other skills, from other repositories
plan-pipeline-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
agent-test-generator
Specialist subagent: Generates comprehensive test suites using TDD patterns. Use only when the user explicitly asks for tests, improved coverage, or test-first development.
python-testing
Expert in Python testing with pytest and test-driven development.
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…
ccc-e2e
Pre-release assessment that fans out via $ccc-fleet into up to three isolated workers (QA audit, unit tests, Playwright E2E) running $ccc-testing lanes, then writes a severity-ranked PASS or FAIL verdict. Use when about to tag a release, after a large merge, or asking is this ready.
dev-tdd
TDD development with Red-Green-Refactor cycle. Use to implement a feature by writing tests BEFORE the code. Trigger automatically when the user asks for TDD, wants to write tests first, mentions "test first", or asks to implement, add, create, fix, correct code, a new feature, a bugfix, or a functionality.