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 AI-Shell-Team/aish --skill aish-add-skillsgit clone --depth 1 https://github.com/AI-Shell-Team/aishWrote 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/ai-shell-team/aish/aish-add-skills)<a href="https://agentmods.dev/skills/ai-shell-team/aish/aish-add-skills"><img src="https://agentmods.dev/badge/skills/ai-shell-team/aish/aish-add-skills/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/ai-shell-team/aish/aish-add-skills"><img src="https://agentmods.dev/badge/skills/ai-shell-team/aish/aish-add-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 7 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 121 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- high Rogue Agent · line 186 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- high Rogue Agent · line 259 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- high Rogue Agent · line 318 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 121 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 259 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00032 | $0.02251 |
| Opus 5 | $0.00016 | $0.01125 |
| Sonnet 5 | $0.00006 | $0.00450 |
| Haiku 4.5 | $0.00003 | $0.00225 |
Grade A, and why
aish-add-skills 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AISH Create Skills
Create reusable skills by extracting methodologies from learning materials or examples.
Quick Example
User: "根据这篇 Docker 教程创建一个 skill"
AI: 读取文档 → 提取步骤 → 生成 skill 结构 → 保存到 ~/.config/aish/skills/
Create Mode Overview
Extract actionable methodologies from learning materials or examples to generate reusable Skills.
When to Use
Use Create Mode when:
- User provides a document/article/tutorial
- User provides an example to learn from
- User says "根据这篇文章创建一个 skill"
- User says "从这个示例学习并创建 skill"
Step 0: Identify Input Type
Critical first step - determine which processing path:
User Input
│
├─ Has teaching intent? ("how to", "steps", "guide")
│ └─ YES → Path A: Methodology Document
│
├─ Is a finished work? (article, design, code, proposal)
│ └─ YES → Path B: Example (Reverse Engineering)
│
└─ Neither? → Tell user this content is not suitable
Path A indicators (Methodology Document):
- Contains "how to", "steps", "method", "guide"
- Has numbered lists or step sequences
- Written with teaching intent
Path B indicators (Example/Output):
- Is a complete work/artifact
- No teaching intent
- Is "the thing itself" rather than "how to make the thing"
Path A: Extract from Methodology Document
A1: Validate Document Suitability
Check if suitable for skill generation (must meet at least 2):
- Has clear goal/outcome
- Has repeatable steps/process
- Has quality criteria
- Has context/scenario description
If not suitable: Tell user honestly and explain why.
A2: Identify Skill Type
| Type | Characteristics | Examples |
|---|---|---|
| How-to | Clear step sequence, input→output | Deploy Docker, Configure CI/CD |
| Decision | Conditions, trade-offs, choices | Choose database, Select framework |
| Framework | Mental model, analysis dimensions | SWOT, 5W1H, First Principles |
| Checklist | Verification list, pass/fail criteria | Code review checklist, Launch checklist |
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.
- 11d ago First seen · 385 lines · 32 tokens per session scan A 769d56b459dd
aish-add-skills is a skill published in the GitHub repository AI-Shell-Team/aish (535 stars, last pushed yesterday), licensed Apache-2.0. It adds 32 tokens to every session and 2,251 once invoked, about $0.0002 per session on Opus 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
completion-script-generator
Generates shell completion scripts for CLI tools. Parses command structure from help output, commander/yargs configs, or manual specification. Produces completions for bash, zsh, and fish that follow each shell's conventions.
taskgo
Maintains a private Git-backed personal project and task control repository using concise current Markdown, derived Git history, ADRs, and status synchronization. Use when tracking tasks, updating project status (STATUS.md), managing ADRs, synchronizing tracker state, delegating tasks to external agents, or generating…
wear-widget
Workflows, checklists, and scripts for reverse-engineering, analyzing, and extracting Wear OS and Android widgets (Glance, AppWidget, ProtoLayout Tiles). Covers manifest declarations, XML configurations, preview asset extraction, and AVD rendering. Use when analyzing APK widget features, extracting widget…
mbo-plan
Plan a new objective end-to-end in this repo's docs/mbo Management-By-Objective system — turn a GitHub issue or a gss draft-PR worktree into consistent design/spec/plan artifacts and track it in docs/mbo/index.md. Use this whenever the user wants to START planning or designing a new feature, skill, CLI, or service…
jetpack
Looks up AndroidX and Jetpack library facts that change between releases: current artifact versions (ALPHA, BETA, RC, STABLE, SNAPSHOT, build IDs), Maven coordinates for classes/packages, direct dependencies, and published source code. Use when looking up AndroidX/Jetpack library versions, finding Maven coordinates…
emumanager
Manages Android SDKs, system images, emulators, and Android Virtual Devices (AVDs). Provides workflows for bootstrapping the SDK, downloading images, and creating, starting, or stopping AVDs across mobile, Wear OS, TV, and Automotive form factors. Use when setting up Android SDK tools, launching or debugging…