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/initxy/noeta/example-commandnpx skills add initxy/noeta --skill example-commandgit clone --depth 1 https://github.com/initxy/noetaWhat 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.00025 | $0.00287 |
| Opus 5 | $0.00013 | $0.00143 |
| Sonnet 5 | $0.00005 | $0.00057 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
example-command 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.
This is a copy
100% identical to example-command — 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.
What it actually says
Example Command (Skill Format)
This demonstrates the skills/<name>/SKILL.md layout for user-invoked slash commands. It is functionally identical to the legacy commands/example-command.md format — both are loaded the same way; only the file layout differs.
Arguments
The user invoked this with: $ARGUMENTS
Instructions
When this skill is invoked:
- Parse the arguments provided by the user
- Perform the requested action using allowed tools
- Report results back to the user
Frontmatter Options Reference
Skills in this layout support these frontmatter fields:
- name: Skill identifier (matches directory name)
- description: Short description shown in /help
- argument-hint: Hints for command arguments shown to user
- allowed-tools: Pre-approved tools for this skill (reduces permission prompts)
- model: Override the model (e.g., "haiku", "sonnet", "opus")
Example Usage
/example-command my-argument
/example-command arg1 arg2
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 First seen · 40 lines · 25 tokens per session scan A d56198166082
example-command is a skill published in the GitHub repository initxy/noeta (9 stars, last pushed 3d ago), licensed Apache-2.0. It adds 25 tokens to every session and 287 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to example-command, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
review-pr
Read-only pull request review workflow with risk analysis, targeted checklists, and Codex subagent consultation.
skill-creator-proposals
Internal tool (not user-invocable). Called by meta-skill-creator's persist step and by opensquilla meta accept CLI (Phase 2) to manage /.opensquilla/proposals/: writeproposal / list / accept. Returns JSON.
penguin-orchestration
Drive PenguinHarness itself from a shell — list and create agents and sessions, send and steer messages mid-flight, and query costs and scheduled tasks via the penguin CLI over the local server.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
skill-creator
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
creating-claude-agents
Use when creating or improving Claude Code agents. Expert guidance on agent file structure, frontmatter, persona definition, tool access, model selection, and validation against schema.