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.
git 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/plugins/jaypokale/chisle/gemini-extension)<a href="https://agentmods.dev/plugins/jaypokale/chisle/gemini-extension"><img src="https://agentmods.dev/badge/plugins/jaypokale/chisle/gemini-extension/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/plugins/jaypokale/chisle/gemini-extension"><img src="https://agentmods.dev/badge/plugins/jaypokale/chisle/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
chisle 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 today.
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
{
"name": "chisle",
"version": "3.8.0",
"description": "Maximum-efficiency dev mode for Gemini. Zero-fluff prose + YAGNI-first code.",
"contextFileName": "GEMINI.md"
}
What ships with it
8 files beside gemini-extension.json 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.
- today Changed 82651a989fb8
- 12d ago Changed 60f91331ad81
- 14d ago Changed f3fe8ecba655
- 15d ago Changed cae09f8ef89d
- 27d ago Changed 00d8031d7ae3
- 1mo ago Changed 2d869376bacf
- 1mo ago Changed 8859ad94f48c
- 1mo ago Changed ab2f1eaa442c
- 1mo ago First seen · 7 lines scan A a033d89c5e6e
chisle is a plugin published in the GitHub repository JayPokale/Chisle (674 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-11.
Other plugins, from other repositories
developer-essentials
Essential developer skills including Git workflows, SQL optimization, error handling, code review, E2E testing, authentication, debugging, and monorepo management.
office-automation
Office Automation — 13 free skills bundled together.
llm-gtd
A portable GTD trusted system for Claude Code — capture, clarify, update, organize, engage, and review commitments in plain Markdown lists under memory/gtd/. Calendar writes fail closed; engage and review stay human-led.
meanwhile
Offer one optional, bounded side quest while a coding agent continues substantial work.
database-cloud-optimization
Database query optimization, cloud cost optimization, and scalability improvements.
statusline-for-claude-code
A dependency-free Node.js status line for Claude Code: model and effort, live git state, context window, prompt-cache state and rate limits on one color-coded line.