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 JayPokale/Chisle --skill chisle-helpgit clone --depth 1 https://github.com/JayPokale/ChisleWrote 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/jaypokale/chisle/chisle-help)<a href="https://agentmods.dev/skills/jaypokale/chisle/chisle-help"><img src="https://agentmods.dev/badge/skills/jaypokale/chisle/chisle-help/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/jaypokale/chisle/chisle-help"><img src="https://agentmods.dev/badge/skills/jaypokale/chisle/chisle-help.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00053 | $0.00284 |
| Opus 5.5 | $0.00021 | $0.00114 |
| Sonnet 5.5 | $0.00011 | $0.00057 |
| Haiku 4.5 | $0.00005 | $0.00028 |
Grade A, and why
chisle-help 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.
What it actually says
Chisle quick reference
What it is: maximum-efficiency dev mode. Zero-fluff prose + YAGNI-first code, always on together.
Commands
| Command | Effect |
|---|---|
/chisle |
Activate |
/chisle-audit [path] |
Audit a diff/file/repo for both code bloat AND prose verbosity |
/chisle-review |
Review the current diff for over-engineering |
stop chisle / normal mode |
Deactivate |
Natural language works: "activate chisle", "chisle mode", "chislify this".
The code ladder
YAGNI → reuse → stdlib → native → installed dep → one line → minimum code.
Statusline
[CHISLE] is shown while active. Configure via
hooks/chisle-statusline.sh (or .ps1 on Windows).
Never minimal about
Input validation, error handling that prevents data loss, security, accessibility, anything you explicitly asked for.
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 Changed 6f6b8faf8b54
- 1mo ago First seen · 37 lines · 53 tokens per session scan A fed650692979
chisle-help is a skill published in the GitHub repository JayPokale/Chisle (714 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 284 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
code-review-excellence
Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
multi-reviewer-patterns
Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results.
simplify
This skill should be used when the user asks to "simplify", "clean up the diff", "run simplify", "simplify the changes", "review changed code for cleanup", explicitly invokes "/simplify", or asks to "commit without simplify", "skip simplify for this commit", or "commit this but skip simplify". Reviews changed code…
refactor
Guides a refactor, cleanup, or restructure with the right decomposition. Use when the user asks to refactor, simplify, extract, or modernize code.
remove-ai-slops
Removes AI-generated code smells from branch changes or an explicit file list behind regression tests. Use when the user asks to clean up, deslop, or remove AI-slop patterns from recent changes.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…