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/desirecore/market/delete-agentnpx skills add desirecore/market --skill delete-agentgit clone --depth 1 https://github.com/desirecore/marketWrote 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/desirecore/market/delete-agent)<a href="https://agentmods.dev/skills/desirecore/market/delete-agent"><img src="https://agentmods.dev/badge/skills/desirecore/market/delete-agent.svg" alt="Measured on agentmods" 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 | $0.00044 | $0.01517 |
| Opus 5 | $0.00022 | $0.00758 |
| Sonnet 5 | $0.00009 | $0.00303 |
| Haiku 4.5 | $0.00004 | $0.00152 |
Grade A, and why
delete-agent 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 3d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
delete-agent skill
L0: One-Sentence Summary
Safely delete a specified Agent and its associated data (filesystem, in-memory state, optional conversation history).
L1: Overview
Meta-skill: list candidates → confirm intent (irreversible) → ask whether to delete history → execute via ManageAgent(action='delete'). Use it to clean up Agents that are no longer used, test/experimental, or need storage reclaimed. Its value is what the tool can't give: candidate filtering with status guidance, and intent confirmation before deletion. The tool guarantees the multi-way refusals (core agent / self / active state) and team cascading.
L2: Detailed Spec
Flow: list deletable Agents → confirm intent and target → ask whether to delete history → execute → receipt.
Stage 1: List Candidates
When the user hasn't named a specific Agent, fetch the list with ManageAgent(action='list') and group by status: offline / error are safe to delete; online / busy / recovery are marked "stop first" (the tool will refuse them) and excluded from the rest of the flow. For details, use ManageAgent(action='get', id). E.g.:
Deletable: Legal Advisor (legal-assistant, offline), Test Bot (test-bot, offline)
Stop first: Data Analyst (data-analyst, online)
Stage 2: Confirm Intent
Confirm the target Agent (name/ID) with the user, explicitly state it is irreversible (config, skills, tools will be permanently deleted), show basic info, and wait for confirmation.
Stage 3: Ask About Deletion Options
Ask whether to also delete all of the Agent's conversation history: yes → deleteRuns=true; no → deleteRuns=false (default, omittable, keeps history).
Stage 4: Execute Deletion
Before the call, reconfirm the target and the deleteRuns choice. The tool submits deletion to the current approval chain; whether an additional dialog appears depends on the caller's approval mode. Do not promise that a dialog will appear unless an approval event is actually shown. Execute:
What ships with it
2 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.
- 3d ago First seen · 107 lines · 44 tokens per session scan A 5083becac11a
delete-agent is a skill published in the GitHub repository desirecore/market (2 stars, last pushed 4d ago), licensed MIT. It adds 44 tokens to every session and 1,517 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-31.
Other skills, from other repositories
skill-authoring
Author SKILL.md skills: frontmatter, validator limits, structure.
a0-plugin-router
Main entry point for all Agent Zero plugin tasks. Routes to specialist skills for creating, reviewing, contributing, managing, or debugging plugins. Use when the user mentions plugins, asks how the plugin system works, wants to build/install/uninstall/publish/debug a plugin, or asks about the Plugin Hub.
a0-plugin-router
Main entry point for all Agent Zero plugin tasks. Routes to specialist skills for creating, reviewing, contributing, managing, or debugging plugins. Use when the user mentions plugins, asks how the plugin system works, wants to build/install/uninstall/publish/debug a plugin, or asks about the Plugin Hub.
create-skill
Wizard for creating new Agent Zero skills. Guides users through creating well-structured SKILL.md files. Use when users want to create custom skills.
agentskills-usage
Teaches AI agents how to use the AgentSkills Registry CLI to search, pull, and push skill bundles.
agent-writer
Write new agent definitions, skill files, and agent configurations. Use when someone asks to "create a new agent", "write a skill", "define an agent", or needs to create reusable AI agent instructions for any platform. This is the meta-skill for creating other skills and agents in the polyagent-skills format.