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/mochow13/keen-code/releasenpx skills add mochow13/keen-code --skill releasegit clone --depth 1 https://github.com/mochow13/keen-codeWhat 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.00010 | $0.00596 |
| Opus 5 | $0.00005 | $0.00298 |
| Sonnet 5 | $0.00002 | $0.00119 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
release 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 2d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Skill
Target version (optional): $ARGUMENTS
If no target version is provided, inspect the latest release tag and commits since that tag before making any changes. Suggest a semantic-version bump to the user and wait for confirmation:
- major for intentional breaking changes.
- minor for backward-compatible features.
- patch for fixes, documentation, dependencies, and internal changes.
Use git tag --sort=-version:refname to identify the latest version tag and git log <latest-tag>..HEAD --oneline to review subsequent commits. Also consider unreleased changelog entries. State the latest tag, the commits considered, the recommended version, and a concise rationale. If there are no commits since the latest tag, say that no release is recommended.
Once a version is supplied or confirmed, use it as the target version for the remaining steps.
Steps
-
Bump versions. Update the version string in both files to the target version:
cmd/main.gonpm/package.json
-
Update
CHANGELOG.md.- Move all entries under
[Unreleased]into a new[X.Y.Z] - YYYY-MM-DDsection below it. - Add a new empty
[Unreleased]section at the top. - Check the commit history for any changes that should be included in the release and were missing in the [Unreleased] section.
- Update the comparison links at the bottom of the file.
- Move all entries under
-
Run the tests.
go test -race ./... -
Verify the npm wrapper.
cd npm && npm pack --dry-run -
Commit the version bump. Stage only the four changed files and commit:
cmd/main.gonpm/package.jsonCHANGELOG.md
-
Create and push the tag.
git tag vX.Y.Z && git push origin main && git push origin vX.Y.ZThe tag must match
npm/package.jsonversion exactly (e.g.v1.2.3). -
Watch the pipelines. Pushing the tag triggers the build and release workflows. Watch them to completion:
gh run watch $(gh run list --limit 1 --json databaseId --jq '.[0].databaseId')If a run fails, inspect logs with
gh run view <run-id> --log-failed.
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.
- 2d ago First seen · 60 lines · 10 tokens per session scan A 03e466060c78
release is a skill published in the GitHub repository mochow13/keen-code (60 stars, last pushed 3d ago), licensed MIT. It adds 10 tokens to every session and 596 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-30.
Other skills, from other repositories
tlamatini-self-update-inclusion
Sweep the whole codebase and keep the SELF-UPDATE pipeline complete — so every new asset/feature added to Tlamatini is actually carried into a release by build.py AND survives (or is correctly replaced by) the self-update swap. Invoke whenever you add/rename a new agent, top-level file or directory, dependency…
tlamatini-self-modify-inclusion
Sweep the whole codebase and keep the SELF-MODIFY source snapshot complete — so the TlamatiniSourceCode/ tree that a --self-modify build ships carries every source/build asset Tlamatini needs to read, modify, and REBUILD herself, with heavy media/secrets correctly omitted+redacted and omitted binaries listed in the…
tlamatini-daily-chat-test
Run the daily automated Tlamatini chat regression — drive a visible Chrome via Playwright, log into agentpage.html, ask up to 1000 curated safe questions one-by-one (Multi-Turn ON, ACPX/Ask-Execs/Exec-Report/Internet OFF), wait for and qualify each answer (heuristic + LLM judge on failures), then write a dated report…
adding-external-mcp
The authoritative reference for adding a NEW external MCP server to Tlamatini universal MCP client layer. Covers the full lifecycle: catalog import, transport selection, activation, runtime provisioning, diagnosis, verification, and troubleshooting. READ THIS BEFORE calling externalmcpimport, before editing…
roblox-studio
Build and edit in Roblox Studio via the Roblox Studio MCP the RIGHT way - preflight the Studio connection, do the whole build in a few big executeluau scripts (not dozens of tiny calls), make REALISTIC terrain with the Terrain VOXEL api driven by Perlin noise (NEVER stacked Parts or concentric layers - those give ugly…
setup-new-acpx-key
Configure the API key (or other credential) for a registered ACPX agentid (claude/codex/cursor/gemini/qwen/copilot/pi/droid/iflow/kilocode/kimi/kiro/opencode/tlamatini) end-to-end across data.keys, config.json (top-level + acpx.agents. .env), regensecrets.py, and verification via acpdoctor.