Context Engineering Kit is a collection of skills, agents, hooks, instructions, commands, and plugins that shape how coding agents use context and carry out development work. It is for developers using Claude Code and other supported coding agents who want more predictable results. The catalogue entries are components from this collection.
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 NeoLabHQ/context-engineering-kit --skill git-notesgit clone --depth 1 https://github.com/NeoLabHQ/context-engineering-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/neolabhq/context-engineering-kit/git-notes)<a href="https://agentmods.dev/skills/neolabhq/context-engineering-kit/git-notes"><img src="https://agentmods.dev/badge/skills/neolabhq/context-engineering-kit/git-notes/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/neolabhq/context-engineering-kit/git-notes"><img src="https://agentmods.dev/badge/skills/neolabhq/context-engineering-kit/git-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00049 | $0.02493 |
| Opus 5.5 | $0.00020 | $0.00997 |
| Sonnet 5.5 | $0.00010 | $0.00499 |
| Haiku 4.5 | $0.00005 | $0.00249 |
Grade A, and why
git-notes 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 1mo 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 1mo ago First seen · 438 lines · 49 tokens per session scan A 70eb256989df
git-notes is a skill published in the GitHub repository NeoLabHQ/context-engineering-kit (1,778 stars, last pushed 1mo ago), licensed GPL-3.0. It adds 49 tokens to every session and 2,493 once invoked, about $0.0002 per session on Opus 5.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
chinese-commit-conventions
A Chinese-language convention for writing Git commit messages, based on Conventional Commits, a standard format that tools can use to classify changes and build changelogs.
Git Commit Writer
Generates conventional commit messages from staged changes or a diff.
commit
Write clear commit messages in conventional commits format. Use when the user is done with changes and wants to commit, says 'commit this', asks for a commit message, or has staged changes ready to go.
friday
Use when the user wants a batch of coding tasks driven through the friday orchestration loop (plan -> Codex implement -> adversarial review -> evidence smoke test -> commit) for web, mobile, backend, CLIs, or libraries. Triggers: "friday this", "run the friday loop", or execute mode "friday this plan .md" when a ready…
git-commit-push
Enforces Git commit standards and conventions when committing and pushing code in Agent Mode. This rule is crucial for keeping track of changes made by agents, and should run whenever the user expresses they want to commit or push code changes made by the agent. This rule should be followed when: 1. the user wants to…
git-commit
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive…