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/bjcoombs/ai-native-toolkit/flawed-sample-skillnpx skills add bjcoombs/ai-native-toolkit --skill flawed-sample-skillgit clone --depth 1 https://github.com/bjcoombs/ai-native-toolkitWhat 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.00036 | $0.00460 |
| Opus 5 | $0.00018 | $0.00230 |
| Sonnet 5 | $0.00007 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
flawed-sample-skill 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.
What it actually says
Commit Message Writer
Write a clean, conventional-commit-formatted message for a set of staged changes.
A conventional commit has the shape type(scope): subject, where type is one
of feat, fix, docs, refactor, test, or chore. The subject is a short
imperative summary. Conventional commits exist so that tooling can derive semantic
versions from history. Semantic versioning, or semver, is a three-part version
number MAJOR.MINOR.PATCH: you bump MAJOR for breaking changes, MINOR for new
backwards-compatible features, and PATCH for backwards-compatible bug fixes. The
versions are ordered, so 1.4.2 is older than 1.4.10, and a leading 0.y.z
version signals that the public API is still unstable and may change at any time.
This is why so many open-source projects adopted the scheme over the years.
Steps
- Run
git diff --stagedand read the full diff to understand what changed. - Decide the conventional-commit
typeand optionalscopefrom the diff. - Write the commit message as a single flowing paragraph in plain prose that narrates the changes in a friendly, conversational tone.
- Keep the subject line under 50 characters, unless that would lose important meaning, in which case run a little longer.
- Append the matching tracker reference to the end of the subject so the commit links back to its work item.
- If the change is large, write a body explaining the reasoning.
- Output the final message in a fenced code block.
Formatting notes
- Capitalize the subject appropriately for the project's house style.
- Add a list of the affected files at the end when it seems helpful.
- Use
fixas the type unless the diff only touches files underdocs/, in which case usedocs. - Always wrap any body text at 72 columns.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 40 lines · 36 tokens per session scan A 260896a69f62
flawed-sample-skill is a skill published in the GitHub repository bjcoombs/ai-native-toolkit (30 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 460 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
commit
Stage and create a Conventional Commits message for the current change.
commit
Create a git commit for the Vision-Agents repo.
commit
Commit current changes with a clear, descriptive message.
moai-ref-git-workflow
Git workflow patterns, branch strategies, conventional commits, and PR templates reference for git operations. Agent-extending skill that amplifies manager-git expertise with production-grade git workflow patterns. NOT for: code implementation, testing, architecture design, documentation content.
commit
Create git commits with good messages. Use when user says "commit", "create commit", or asks to commit changes.
git-commit
Create git commits using Nimbalyst's interactive commit proposal widget. ONLY use when the user explicitly clicks "Commit with AI" button or asks for "smart commit". For regular commit requests, use standard git commands instead.