agentmods.dev

kanban-md: Skill for Claude Code

.agents/skills/evolve-kanban-md-formats/SKILL.md

evolve-kanban-md-formats is a skill for Claude Code from antopolskiy/kanban-md. It costs 63 tokens per session (672 once invoked), scanned A, original, MIT.

A development guide for changing kanban-md configuration files and task metadata without breaking existing boards. It treats configuration and Markdown front matter as stored data that upgrades must continue to read.

In plain words
What is it for?
Use it when adding configuration fields, changing defaults, updating task metadata, or maintaining version and migration code. Do not use it for output-only changes or ordinary task edits.
Why use it?
It prevents schema changes from making older boards unusable. It also requires explicit migrations and compatibility fixtures, which are test files containing older data examples.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is antopolskiy/kanban-md's own configuration. It tells Claude Code how to work on kanban-md itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything kanban-md configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is go test -run Compat ./internal/config/ ./internal/task/.

not rated 226repo 23d ago A scan 63 tokens original MIT
View source ↗ antopolskiy/kanban-md
Reuse

Borrowing it

Nothing to install: this file belongs to antopolskiy/kanban-md. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/antopolskiy/kanban-md/main/.agents/skills/evolve-kanban-md-formats/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/antopolskiy/kanban-md

Made for: Claude Code.

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.

agentmods badge for evolve-kanban-md-formats

README.md
[![agentmods](https://agentmods.dev/badge/skills/antopolskiy/kanban-md/evolve-kanban-md-formats/github.svg)](https://agentmods.dev/skills/antopolskiy/kanban-md/evolve-kanban-md-formats)
Your own site
<a href="https://agentmods.dev/skills/antopolskiy/kanban-md/evolve-kanban-md-formats"><img src="https://agentmods.dev/badge/skills/antopolskiy/kanban-md/evolve-kanban-md-formats/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.

agentmods 80×15 button for evolve-kanban-md-formats

Your own site · 80×15
<a href="https://agentmods.dev/skills/antopolskiy/kanban-md/evolve-kanban-md-formats"><img src="https://agentmods.dev/badge/skills/antopolskiy/kanban-md/evolve-kanban-md-formats.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 672 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00063 $0.00672
Opus 5.5 $0.00025 $0.00269
Sonnet 5.5 $0.00013 $0.00134
Haiku 4.5 $0.00006 $0.00067

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

Security

Grade A, and why

evolve-kanban-md-formats 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 23d 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.

.agents/skills/evolve-kanban-md-formats/SKILL.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Evolve kanban-md formats

Treat config.yml and task frontmatter as durable user data contracts. Existing boards must remain readable after an upgrade, and migrations must be explicit, ordered, and covered by compatibility fixtures.

Configuration design

  • Collocate new or migrated per-column settings with the corresponding entry in statuses. This applies to settings such as show_duration, require_claim, and WIP limits.
  • The existing top-level wip_limits map is a compatibility shape, not a model for new per-column settings. Migrate it only as part of an intentional schema revision.
  • Prefer backward-compatible defaults and prospective enforcement. Do not make an existing board invalid merely because a new optional policy exists.

Config schema changes

  1. Inspect internal/config/defaults.go, internal/config/migrate.go, and every existing compatibility fixture before editing the schema.
  2. Increment CurrentVersion in internal/config/defaults.go.
  3. Add a migration from the previous version in internal/config/migrate.go, register it in the migrations map, and increment cfg.Version in the migration.
  4. Create internal/config/testdata/compat/vN/, where N is the old version. Start from the previous fixture and make it representative of the format being migrated, including sample task files when relevant.
  5. Add or extend internal/config/compat_test.go assertions so the old fixture loads through all migrations and exposes the intended current values.
  6. Update the generated-config example and user guidance when the serialized shape or defaults change.

Never skip intermediate versions or mutate an old fixture to look like the new format; fixtures document what users already have on disk.

Task frontmatter changes

  • Additive optional fields with omitempty preserve old files that omit them, but still require a fixture and parsing assertion for the new field.
  • Do not rename or remove an existing YAML tag. If semantics must evolve, keep reading the old representation and migrate or translate it explicitly.
  • Exercise new task fields in internal/task/testdata/compat/v1/tasks/, or create a new versioned fixture directory when the task format itself becomes versioned or requires migration.
  • Add assertions in internal/task/compat_test.go for parsing, zero values, and round-trip behavior where relevant.

Read the full file on GitHub · 73 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.

  1. 23d ago First seen · 73 lines · 63 tokens per session scan A d294fdfc011b

Subscribe to this mod's changes

evolve-kanban-md-formats is a skill published in the GitHub repository antopolskiy/kanban-md (226 stars, last pushed 23d ago), licensed MIT. It adds 63 tokens to every session and 672 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-10-06.

Testingai-agentsclideveloper-toolsgokanbanmarkdown
Related

Other skills, from other repositories

code-guidelines-go

Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…

dimetron/pi-go · 124 tokens

go-127

What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…

dimetron/pi-go · 177 tokens

bubbletea-testing

Use this skill whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go. Triggers include any mention of testing Bubble Tea models, teatest, golden file testing for TUIs, testing tea.Cmd or tea.Msg, snapshot testing terminal output, or writing tests for any Go CLI/TUI that uses the Elm…

dimetron/pi-go · 139 tokens

vhs-e2e-gif

Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…

dimetron/pi-go · 106 tokens

check-linters-before-commit

Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.

dimetron/pi-go · 30 tokens

test-fix

Diagnose and minimally fix a failing test, then re-run.

patriceckhart/zot · 17 tokens