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 Cantara/kcp-harness --skill resign-knowledge-yamlgit clone --depth 1 https://github.com/Cantara/kcp-harnessWrote 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/cantara/kcp-harness/resign-knowledge-yaml)<a href="https://agentmods.dev/skills/cantara/kcp-harness/resign-knowledge-yaml"><img src="https://agentmods.dev/badge/skills/cantara/kcp-harness/resign-knowledge-yaml/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/cantara/kcp-harness/resign-knowledge-yaml"><img src="https://agentmods.dev/badge/skills/cantara/kcp-harness/resign-knowledge-yaml.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.00000 | $0.00422 |
| Opus 5 | $0.00000 | $0.00211 |
| Sonnet 5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
resign-knowledge-yaml 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 9d 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
Resign knowledge.yaml
Governed skill: recover from an invalidated knowledge.yaml.sig after editing knowledge.yaml
on a PR branch — this repo's own test suite verifies that signature, so an unsigned edit
self-blocks its own PR, and a merge to main cannot fix a check that is already blocking
the merge.
Preconditions
knowledge.yamlwas edited on a branch that is NOTmain/master(a push tomaintriggerssign-kcp.ymlautomatically — this skill is for the PR-branch case, where thatpushtrigger never fires).- You have permission to dispatch workflows on this repo; the signing key itself lives in
Cantara/.githuband is reached viasecrets: inherit, not held locally.
Steps
- (read) Confirm this is the actual failure: CI red on the manifest-signature check, and
knowledge.yaml(not just.sig) was touched in the diff. - (bash)
gh workflow run sign-kcp.yml --ref <your-branch>— itsworkflow_dispatchtrigger exists specifically so the manifest can be re-signed against a PR branch on demand, not just againstmain. - (bash) Wait for the run to finish, then
git pullon your branch — the workflow commits the refreshedknowledge.yaml.sigback to the branch it ran against. - (read) Re-run or re-check CI on the PR; confirm the signature check is now green.
Verification
knowledge.yaml.sig on the branch has a new commit from the signing workflow, and the
manifest-signature CI check is green on the PR.
Rollback
If the dispatch fails or the signing secret is unavailable to your branch: do not hand-edit
knowledge.yaml.sig or weaken signature verification to unblock the PR — page whoever holds
the Cantara/.github signing secret instead.
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.
- 9d ago First seen · 33 lines · 0 tokens per session scan A f24d6e0e9aa4
resign-knowledge-yaml is a skill published in the GitHub repository Cantara/kcp-harness (0 stars, last pushed 15d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 422 tokens. 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.