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/archastro/archagents/archagent-build-scriptnpx skills add ArchAstro/archagents --skill archagent-build-scriptgit clone --depth 1 https://github.com/ArchAstro/archagentsWhat 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.00070 | $0.02388 |
| Opus 5 | $0.00035 | $0.01194 |
| Sonnet 5 | $0.00014 | $0.00478 |
| Haiku 4.5 | $0.00007 | $0.00239 |
Grade A, and why
archagent-build-script 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 2d 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
94% identical to build-script — 11 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ArchAstro Script Builder
Write, test, and deploy scripts — custom logic that powers agent tools, workflow nodes, and routines.
This skill assumes the ArchAgent CLI is already installed and authenticated. Install or upgrade archagent if missing, and run archagent auth login <email> if not authenticated.
What is a Script?
Scripts are expression-oriented custom logic written in the ArchAstro script language. They can be used as:
- Custom tool handlers: Agent calls a tool → script runs → result returned to agent
- Workflow graph script steps: Script logic used inside a workflow graph
- Routine handlers: A scheduled routine runs the script directly
Scripts are first-class resources with their own CRUD, validation, and execution commands.
Use the dedicated top-level script resource for the normal authoring loop: archagent list scripts, describe script, create script, update script, validate script, run script, and describe scriptdocs.
Always Start with State
Every invocation must begin by understanding the current context:
archagent auth status
archagent list scripts
Determine:
- Is the user creating a new script or editing an existing one?
- What will this script be used for? (tool, workflow node, routine)
- What external APIs or data does it need to access?
Routing
User wants to write a new script
Phase 1: Get the language reference
Always start by fetching the live reference — do not write scripts from memory:
archagent describe scriptdocs
Use the top-level script commands, not describe configsample/validate config, for the normal authoring loop.
Create a script from a local source file:
archagent create script --id my-script --file ./scripts/my-script.agentscript
Or let the CLI start from its built-in sample if you do not pass --source or --file:
archagent create script --id my-script
Phase 2: Understand the requirements
Ask the user:
- What should the script do?
- What inputs will it receive? (accessible via
$JSONPath) - Does it need environment variables? (accessible via
env.KEY) - Does it need to make HTTP calls?
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.
- 2d ago First seen · 291 lines · 70 tokens per session scan A f90cb216e400
archagent-build-script is a skill published in the GitHub repository ArchAstro/archagents (5 stars, last pushed 16d ago), licensed MIT. It adds 70 tokens to every session and 2,388 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to build-script, differing in 11 lines, and is treated as a copy.
Other skills, from other repositories
create-agent
Help users create and configure openma managed agents through conversation. Trigger when users say "create an agent", "I need an agent that...", "set up an agent for", "build me a bot", or describe a task to automate. Also trigger for "Create with AI" from Dashboard. Also use when users ask about the openma platform…
openma
Use the openma platform to build, deploy, and manage AI agents. Trigger when users want to create agents, start sessions, manage environments, configure model cards, handle vaults/credentials, install skills, connect MCP servers, or interact with the openma HTTP API. Also trigger when users mention "oma", "openma"…
openhermit-admin
Explain what OpenHermit is and how to deploy and administer it — setup, CLI, gateway, agent config, API. Use when the user asks about installing, operating, or administering an OpenHermit deployment. For how agents behave for their owners/users/guests, see openhermit-guide.
skill-creator
Create, structure, and validate new skills. Use when designing a skill, scaffolding a skill directory, or improving an existing skill.
openhermit-guide
Explain how an OpenHermit agent behaves for the people interacting with it — owners, users, and guests. Covers roles, identity linking, the agent's tools, access levels, channels, the policy model, and the approval flow. Use when someone asks how an OpenHermit agent works from a caller's perspective. For deploying or…
mcporter
List, auth, and call MCP servers/tools from the terminal.