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/gen-verse/past-bench/a0-developmentnpx skills add Gen-Verse/PAST-Bench --skill a0-developmentgit clone --depth 1 https://github.com/Gen-Verse/PAST-BenchWrote 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/gen-verse/past-bench/a0-development)<a href="https://agentmods.dev/skills/gen-verse/past-bench/a0-development"><img src="https://agentmods.dev/badge/skills/gen-verse/past-bench/a0-development.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.00052 | $0.07437 |
| Opus 5 | $0.00026 | $0.03719 |
| Sonnet 5 | $0.00010 | $0.01487 |
| Haiku 4.5 | $0.00005 | $0.00744 |
Grade C, and why
a0-development scanned grade C with 1 finding 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 5d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- /a0/usr/agents/data-analyst/prompts/agent.system.main.role.md --> How it starts
The opening of the file, as written. The whole thing — 844 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Zero Development Guide
This skill provides comprehensive, accurate guidance for extending and building features for Agent Zero. Use it when you need to:
- Understand the architecture and project layout
- Create new Tools for agent capabilities
- Add Extensions to hook into the framework lifecycle
- Build API Endpoints for the Web UI
- Create Agent Profiles (subordinates) with custom prompts
- Understand and extend the Prompt System
- Create Skills (see the dedicated
create-skillskill for the full wizard) - Work with Projects and workspace configuration
Path convention: Throughout this guide,
/a0/refers to the framework root — this is/a0/inside Docker, or your local repository root in development. All paths are relative to this root.
[!IMPORTANT] Plugins are the primary way to extend Agent Zero. Most new tools, extensions, and prompts should be packaged as plugins. For all plugin tasks (create, review, manage, debug, contribute), load the
a0-plugin-routerskill which routes to the appropriate specialist. This guide covers the underlying framework patterns that plugins build upon.
Related skills: a0-plugin-router (plugin tasks) | create-skill (skill creation wizard) | a0-create-plugin | a0-review-plugin | a0-manage-plugin | a0-contribute-plugin | a0-debug-plugin
Architecture Overview
Project Layout
/a0/ # Framework root
├── agent.py # Core Agent + AgentContext + AgentConfig classes
├── initialize.py # Agent initialization logic
├── models.py # Model definitions
├── run_ui.py # Web UI entry point
│
├── tools/ # Core tools (search, response, browser, etc.)
├── extensions/
│ ├── python/ # Python lifecycle extensions
│ │ ├── <hook_point>/ # e.g., agent_init/, system_prompt/, etc.
│ │ │ └── _NN_name.py # Numbered extension files
│ │ └── _functions/ # Implicit @extensible decorator extensions
│ └── webui/ # JavaScript WebUI extensions
│ └── <hook_point>/ # e.g., json_api_call_before/
│ └── name.js
├── api/ # Flask API endpoint handlers
├── helpers/ # Framework utilities and base classes
│ ├── tool.py # Tool + Response base classes
│ ├── extension.py # Extension base class + @extensible decorator
│ ├── api.py # ApiHandler base class
│ ├── files.py # File operations + prompt reading
│ ├── plugins.py # Plugin system manager
│ ├── print_style.py # Console output formatting
│ └── ... # Many more utility modules
│
├── prompts/ # Core prompt fragments (system, tools, framework)
├── agents/ # Agent profiles (subordinate specializations)
│ ├── default/ # Base profile (inherited by others)
│ ├── agent0/ # Main user-facing agent
│ ├── developer/ # Developer subordinate
│ ├── hacker/ # Security subordinate
│ ├── researcher/ # Research subordinate
│ └── _example/ # Example profile with tool + extension samples
│
├── plugins/ # Core plugins (tools, extensions, prompts)
│ ├── _code_execution/ # Terminal/Python/Node.js execution
│ ├── _memory/ # Persistent memory system
│ ├── _text_editor/ # File read/write/patch
│ ├── _model_config/ # LLM model selection
│ ├── _infection_check/ # Prompt injection safety
│ └── ... # More core plugins
│
├── skills/ # Core skills (SKILL.md bundles)
├── knowledge/ # Knowledge base files
├── webui/ # Web UI frontend
├── docs/ # Documentation
│
└── usr/ # User-space (survives updates)
├── agents/ # User-created agent profiles
├── plugins/ # User-installed plugins
├── skills/ # User-created skills
├── knowledge/ # User knowledge base files
├── extensions/ # Standalone user extensions (created on demand; prefer plugins instead)
├── projects/ # Project workspaces (created on demand when user adds projects via UI)
└── workdir/ # Default working directory
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.
- 5d ago First seen · 844 lines · 52 tokens per session scan C 4ec8f9add6b2
a0-development is a skill published in the GitHub repository Gen-Verse/PAST-Bench (25 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 7,437 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
a0-development
Development guide for extending Agent Zero from current source and DOX. Use for framework architecture, tools, extensions, API/WebUI handlers, agent profiles, prompts, skills, projects, runtime boundaries, and contribution workflow. Load the focused reference files before giving implementation guidance.
frontmcp-development
Use when building any FrontMCP server component other than a tool (for tools, use create-tool). Covers @Resource static resources and parameterized URI templates; @Prompt reusable prompts (RAG, multi-turn); @Provider singleton dependency-injection providers (database pools, API clients); @Agent autonomous LLM agents…
composio
Use 1000+ external apps via Composio - either directly through the CLI or by building AI agents and apps with the SDK.
agent-development
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development…
skill-creator
Create or improve Zhin Agent skills (SKILL.md). Use when asked to add a skill, write SKILL.md, document a repeatable agent workflow, or refine skill frontmatter/keywords. Triggers: 创建技能, 写 SKILL, skill-creator, 加 skill.
incident-response-skill
A skill that uses object-style tool references with purpose descriptions and required flags, plus strict validation.