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/ArcBlock/agent-skillsWrote 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/commands/arcblock/agent-skills/init)<a href="https://agentmods.dev/commands/arcblock/agent-skills/init"><img src="https://agentmods.dev/badge/commands/arcblock/agent-skills/init/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/commands/arcblock/agent-skills/init"><img src="https://agentmods.dev/badge/commands/arcblock/agent-skills/init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00013 | $0.00753 |
| Opus 5.5 | $0.00005 | $0.00301 |
| Sonnet 5.5 | $0.00003 | $0.00151 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
init 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.
This is a copy
100% identical to init — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Plugin
Create the standard directory structure and files for a new Claude Code plugin.
Arguments
$1(required): Plugin name in kebab-case (e.g.,my-awesome-plugin)
What This Command Does
- Creates the plugin directory structure:
.claude-plugin/withplugin.jsoncommands/directoryagents/directoryskills/directoryhooks/directory withhooks.jsonscripts/directory
- Generates a starter
plugin.jsonwith the provided name - Creates a README.md template
- Provides next steps
Instructions
Validation
First, validate the plugin name:
- Must be provided (not empty)
- Should be kebab-case (lowercase with hyphens)
- Should not contain spaces or special characters
If validation fails, explain the requirements and ask for a valid name.
Create Directory Structure
Create these directories:
$1/
├── .claude-plugin/
├── commands/
├── agents/
├── skills/
├── hooks/
└── scripts/
Create plugin.json
Create .claude-plugin/plugin.json with this template:
{
"name": "$1",
"version": "0.1.0",
"description": "Brief description of what this plugin does",
"author": {
"name": "Your Name",
"email": "[email protected]"
},
"license": "MIT",
"keywords": ["keyword1", "keyword2"]
}
Create hooks.json
Create hooks/hooks.json with a basic structure:
{
"description": "Plugin hooks",
"hooks": {}
}
Create README.md
Create README.md with this template:
# $1
[Brief description of what this plugin does]
## Installation
```bash
/plugin install $1@marketplace-name
Commands
[List commands here]
Usage
[Provide examples]
### Create Validation Script
Create `scripts/validate-plugin.sh` with executable permissions:
```bash
#!/usr/bin/env bash
set -euo pipefail
# Basic plugin structure validation
[ -f ".claude-plugin/plugin.json" ] || { echo "Missing plugin.json" >&2; exit 2; }
exit 0
Make it executable: chmod +x scripts/validate-plugin.sh
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 · 150 lines · 13 tokens per session scan A 2ad5ef2dcb47
init is a command published in the GitHub repository ArcBlock/agent-skills (5 stars, last pushed 13d ago), licensed MIT. It adds 13 tokens to every session and 753 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to init, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.