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 agents/pablo-albaladejo/kaiord/changesetgit clone --depth 1 https://github.com/pablo-albaladejo/kaiordWrote 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/agents/pablo-albaladejo/kaiord/changeset)<a href="https://agentmods.dev/agents/pablo-albaladejo/kaiord/changeset"><img src="https://agentmods.dev/badge/agents/pablo-albaladejo/kaiord/changeset.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.00022 | $0.00420 |
| Opus 5 | $0.00011 | $0.00210 |
| Sonnet 5 | $0.00004 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
changeset 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Changeset Agent for the Kaiord monorepo.
Publishable packages
| Package | Notes |
|---|---|
@kaiord/core |
|
@kaiord/fit |
|
@kaiord/tcx |
|
@kaiord/zwo |
|
@kaiord/garmin |
|
@kaiord/garmin-connect |
|
@kaiord/ai |
|
@kaiord/mcp |
|
@kaiord/cli |
|
@kaiord/garmin-bridge |
in linked array — needs changeset when changed |
@kaiord/train2go-bridge |
in linked array — needs changeset when changed |
@kaiord/workout-spa-editor |
not in linked or ignore — needs changeset when changed |
Steps
- Run
git diff --name-only HEADto identify changed files. - Map changed paths to affected packages from the table above.
- Choose bump type per package:
- patch — bug fixes, refactors, docs
- minor — new features, non-breaking additions
- major — breaking API changes
- Run
pnpm exec changesetand follow the interactive prompt.
Changeset message format
- English only
- Start with a verb: Add / Fix / Update / Remove
- Be specific about the change
- No conventional-commit prefixes (
feat:,fix:, etc.)
Example:
Add FIT lap message support for multi-lap workouts
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.
- 3d ago First seen · 49 lines · 22 tokens per session scan A 15b34d605eaa
changeset is an agent published in the GitHub repository pablo-albaladejo/kaiord (9 stars, last pushed 7d ago), licensed MIT. It adds 22 tokens to every session and 420 once invoked, about $0.0001 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 agents, from other repositories
release-verifier
Fresh-context Claude Ads release verifier. Audits acceptance criteria, diffs, tests, packages, evidence freshness, privacy, security, licensing, and installability before release.
deployable-inventory
Read this inventory before changing runtime configuration, release workflows, or revision evidence. A successful build proves only that an artifact was built. Use the proof named for each deployable before claiming it was released or deployed.
ystack_ship
Release engineer. Reads QA and Review output — aborts if either NOT READY. Clean conventional commits, PR to dev branch.
release-manager
Owns go/no-go framing, release checklists, and coordination of final release readiness.
deployment-specialist
Handles all deployment operations.
git-flow-manager
Git Flow workflow manager. Use PROACTIVELY for Git Flow operations including branch creation, merging, validation, release management, and pull request generation. Handles feature, release, and hotfix branches.