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 instructions/nomadamas/k-skill/agents-mdgit clone --depth 1 https://github.com/NomaDamas/k-skillWhat 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.02471 | $0.02471 |
| Opus 5 | $0.01236 | $0.01236 |
| Sonnet 5 | $0.00494 | $0.00494 |
| Haiku 4.5 | $0.00247 | $0.00247 |
Grade A, and why
k-skill AGENTS.md 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
k-skill repository instructions
This repository inherits the broader oh-my-codex guidance from the parent environment. These rules are repo-specific and apply to everything under this directory.
Release automation rules
- Node packages live under
packages/*and use npm workspaces. - Node package releases use Changesets. Do not hand-edit package versions only to cut a release; add a
.changeset/*.mdfile instead. - npm publish is automated from GitHub Actions and should happen only after the bot-generated Version Packages PR is merged into
main. - Python packages live under
python-packages/*and use release-please. Until a real Python package exists, keep the Python release workflow as scaffold-only. - PyPI publish should run only when release-please reports
release_created=truefor a concrete package path. - Prefer trusted publishing via OIDC for npm and PyPI. Do not introduce long-lived registry tokens unless trusted publishing is unavailable.
Verification rules
- For release or packaging changes, run
npm run ci. - Keep release docs, workflow files, and package metadata aligned in the same change.
Skill deletion rules
- When a skill is removed, delete its source, generated copies, package code, tests, fixtures, documentation, proxy helpers, and registry metadata from the repository.
- Do not preserve removed skills or related code under
legacy/,archive/,deprecated/,retired/, or any similar in-repository holding directory. - If future reimplementation may be useful, track the intent and requirements in a GitHub issue; Git history remains the source for retrieving deleted implementations.
Testing anti-patterns
- Never write tests that assert
.changeset/*.mdfiles exist. Changesets are consumed (deleted) bychangeset versionduring the release flow. Any test guarding changeset file presence will break CI on the version-bump commit and block the release pipeline. - Never write tests that pin a workspace package's
versionfield (inpackage.jsonorpackage-lock.json).changeset versionbumps these on every release, so any hardcoded version assertion will fail the next release commit and block the npm publish pipeline. Stable invariants likename,license,engines.node, or workspace link metadata are fine to assert; theversionis not.
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 · 99 lines · 2,471 tokens per session scan A 8b61811d441a
k-skill AGENTS.md is an instructions file published in the GitHub repository NomaDamas/k-skill (7,393 stars, last pushed yesterday), licensed MIT. It adds 2,471 tokens to every session, about $0.0124 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.