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 autohandai/code-cli --skill extension-buildergit clone --depth 1 https://github.com/autohandai/code-cliWrote 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/autohandai/code-cli/extension-builder)<a href="https://agentmods.dev/skills/autohandai/code-cli/extension-builder"><img src="https://agentmods.dev/badge/skills/autohandai/code-cli/extension-builder/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/autohandai/code-cli/extension-builder"><img src="https://agentmods.dev/badge/skills/autohandai/code-cli/extension-builder.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.00069 | $0.01259 |
| Opus 5.5 | $0.00028 | $0.00504 |
| Sonnet 5.5 | $0.00014 | $0.00252 |
| Haiku 4.5 | $0.00007 | $0.00126 |
Grade A, and why
extension-builder 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 yesterday.
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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Autohand extensions
Turn the user's description or source package into a working Autohand extension. Finish with an installed result verified in the current REPL when the user asked for installation. Use the trusted runtime contract for commands, TUI, keybindings, flags, hooks, providers, or permission policy; modify Autohand itself only when the versioned extension API cannot represent the behavior and the current workspace is the Autohand source repository.
Load the relevant contract
- Read references/autohand-extension-v1.md before creating or changing an Autohand extension package.
- Also read references/pi-compatibility.md when the request mentions Pi, pi-mono, a
pipackage manifest,registerTool,registerCommand, Pi events, or Pi skills.
Workflow
- Inspect the exact target, repository instructions, existing manifest, related contributions, and tests before editing.
- Turn the request into observable capabilities: tool names and parameters, agent behavior, Agent Skills, permission boundaries, lifecycle behavior, and installation scope.
- Choose the delivery shape:
- Use declarative contributions for shell-template tools, focused agents, and Agent Skills.
- Use a trusted runtime entrypoint for slash commands, Ink views, status/help segments, shortcuts, flags, hooks, providers, or permission policies.
- Extend the existing package when the user named one; preserve its id and compatible behavior.
- Change Autohand source only when the versioned runtime API cannot represent the required behavior.
- Use a hybrid only when the boundary is explicit and each part is independently testable.
- Write a failing test or validation fixture before production code. For TUI, startup, prompt, menu, or screen behavior, add Tuistory coverage.
- Implement the smallest complete capability. Reuse existing tools, permission checks, hooks, registries, and runtime layers.
- Validate and exercise the complete lifecycle:
What ships with it
3 files 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.
- yesterday Changed · +1 lines 09d18e3ba061
- 1mo ago First seen · 66 lines · 69 tokens per session scan A d60bbdbae0e1
extension-builder is a skill published in the GitHub repository autohandai/code-cli (210 stars, last pushed 2d ago), licensed Apache-2.0. It adds 69 tokens to every session and 1,259 once invoked, about $0.0003 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
neuron-laravel-integration
Integrate Neuron AI agents into a Laravel 13 app the framework-native way — setup checklist (App\Neuron layout, config/services.php keys, one migration, NeuronServiceProvider, bootstrap/app.php exception mapping, neuron:evaluate), container-built agents bound per thread with for(), thread authorization, JSON and…
neuron-evaluation
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
neuron-agent
Create, configure, and extend Neuron AI agents in PHP using providers, tools, chat history, memory, and custom workflow nodes. Use for Neuron Agent implementation, configuration, conversation lifecycle, and input/output extensions.
neuron-rag
Implement RAG (Retrieval-Augmented Generation) with Neuron AI including vector stores, embeddings providers, document loaders, retrieval strategies, and metadata filtering. Use this skill whenever the user mentions RAG, retrieval, vector search, document retrieval, semantic search, knowledge bases, chat with…
neuron-structured-output
Design and implement structured output classes for Neuron AI agents using SchemaProperty attributes and validation rules. Use this skill when the user mentions structured output, JSON schema extraction, data validation, output classes, DTOs for AI responses, extracting structured data from LLM, or configuring property…
neuron-tool-approval
Implement human-in-the-loop tool approval flows with Neuron AI agents — gating risky tools behind approve/deny decisions, rendering approval UIs from chat history, submitting decisions, and building a single endpoint that handles both conversation turns and approval continuations. Use this skill whenever the user…