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/oikon48/claudecode-book/taskboard-feature-devnpx 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.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.00067 | $0.00202 |
| Opus 5 | $0.00034 | $0.00101 |
| Sonnet 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 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.
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.
- 4d 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 (7 stars, last pushed 22d ago), licensed MIT. It adds 67 tokens to every session and 202 once invoked, about $0.0003 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-31.
Other skills, from other repositories
tdd-rust
TDD workflow for RTK filter development. Red-Green-Refactor with Rust idioms. Real fixtures, token savings assertions, snapshot tests with insta. Auto-triggers on new filter implementation.
rtk-tdd
Enforces TDD (Red-Green-Refactor) for Rust development. Auto-triggers on implementation, testing, refactoring, and bug fixing tasks. Provides Rust-idiomatic testing patterns with anyhow/thiserror, cfg(test), and Arrange-Act-Assert workflow.
writing-skills
当创建新技能、编辑现有技能或在部署前验证技能是否有效时使用.
test-driven-development
在实现任何功能或修复 bug 时使用，在编写实现代码之前.
test-driven-development
Use when the user explicitly requests strict or test-first TDD, or when the current conversation already contains an explicit TDD Route: strict decision from another Aegis workflow.
old-coder
Evidence-first development — surround the implementation with an executable spec and a gauntlet of constraints (tests, types, coverage, mutation) so line-by-line review becomes optional. Use when the user explicitly asks for high-assurance or evidence-first work ("reliable", "TDD", "prove it works", "I won't read the…