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 deepklarity/harness-kit --skill hk-changeloggit clone --depth 1 https://github.com/deepklarity/harness-kitWrote 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/deepklarity/harness-kit/hk-changelog)<a href="https://agentmods.dev/skills/deepklarity/harness-kit/hk-changelog"><img src="https://agentmods.dev/badge/skills/deepklarity/harness-kit/hk-changelog/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/deepklarity/harness-kit/hk-changelog"><img src="https://agentmods.dev/badge/skills/deepklarity/harness-kit/hk-changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.01628 |
| Opus 5 | $0.00018 | $0.00814 |
| Sonnet 5 | $0.00007 | $0.00326 |
| Haiku 4.5 | $0.00004 | $0.00163 |
Grade A, and why
hk-changelog 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 10d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Creator
Generate a changelog entry from git changes, prepend it to CHANGELOG.md, and optionally commit + raise a PR.
Usage
/hk-changelog → full flow: write + commit + PR
/hk-changelog --dry-run → print the entry only (no file changes)
/hk-changelog --commit → write + commit (no PR)
Arguments are passed via $ARGUMENTS.
Instructions
Step 1: Parse arguments
Check $ARGUMENTS for --dry-run or --commit. Default behavior (no args) is the full flow: write, commit, and open a PR.
Step 2: Gather raw git data
Run these commands to collect the raw material. This is mechanical — just capture the output:
# What branch are we on?
git rev-parse --abbrev-ref HEAD
# Commits on this branch that aren't on main
git log main..HEAD --oneline --no-merges 2>/dev/null
# File-level summary
git diff --stat main...HEAD 2>/dev/null
git diff main...HEAD --name-status 2>/dev/null
# Unstaged/untracked
git diff --stat HEAD
git diff --name-status HEAD
git status --short | grep "^??"
If there are no commits diverging from main AND no staged/unstaged changes, tell the user there's nothing to changelog and stop.
If on main with no diverging commits, fall back to diffing against the previous commit:
git log -1 --oneline
git diff HEAD~1 --stat
git diff HEAD~1 --name-status
Also read the existing CHANGELOG.md so the subagent can match the format.
Step 3: Delegate to haiku subagent
Use the Task tool with subagent_type: "general-purpose" and model: "haiku" to do the heavy lifting. The subagent reads diffs, understands the changes, and generates the changelog entry.
Pass the subagent a prompt containing:
- All the git output from Step 2
- The existing
CHANGELOG.mdcontent (for format reference) - The full generation rules below
- A clear instruction: "Read the actual diffs by subsystem, then generate a changelog entry. Return ONLY the markdown entry, nothing else."
The subagent prompt must include these instructions:
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.
- 10d ago First seen · 182 lines · 36 tokens per session scan A 16d1a184ffba
hk-changelog is a skill published in the GitHub repository deepklarity/harness-kit (97 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 1,628 once invoked, about $0.0002 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-30.
Other skills, from other repositories
publish-harness
Publish a generated harness to npm — runs the smoke test, signs the witness manifest, and dispatches npm publish --provenance from your tagged release.
github-deep-research
Conduct multi-round deep research on any GitHub Repo. Use when users request comprehensive analysis, timeline reconstruction, competitive analysis, or in-depth investigation of GitHub. Produces structured markdown reports with executive summaries, chronological timelines, metrics analysis, and Mermaid diagrams.…
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
neuron-structured-output
Design and implement structured output classes for Neuron AI agents using SchemaProperty attributes and validation rules. Use this skill when the user mentions structured output, JSON schema extraction, data validation, output classes, DTOs for AI responses, extracting structured data from LLM, or configuring property…
merge-strategy
Git merge strategies, conflict resolution approaches, merge vs rebase recommendations, and branch integration patterns in sidecar. Covers pull strategy menu, direct merge workflow, squash merge, commit message templates, configurable defaults, and protected branches. Use when working on git merge features or making…
comet-github-issue-fix
A workflow for fixing a confirmed Comet-related GitHub issue or review blocker within an isolated scope. It covers matching the work to the relevant workflow, testing the change, checking runtime results, and preparing a careful handoff.