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-author-agentnpx skills add ArchAstro/archagents --skill archagent-author-agentgit clone --depth 1 https://github.com/ArchAstro/archagentsWrote 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/archastro/archagents/archagent-author-agent)<a href="https://agentmods.dev/skills/archastro/archagents/archagent-author-agent"><img src="https://agentmods.dev/badge/skills/archastro/archagents/archagent-author-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.00072 | $0.01166 |
| Opus 5 | $0.00036 | $0.00583 |
| Sonnet 5 | $0.00014 | $0.00233 |
| Haiku 4.5 | $0.00007 | $0.00117 |
Grade A, and why
archagent-author-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 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.
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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ArchAstro Agent Authoring
Create or update the config files for a config-driven ArchAstro agent before deployment.
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.
Always Start with State
Every invocation must begin by understanding the current project state:
archagent auth status
If the user is in a repo, inspect whether a configs/ directory already exists and whether the agent already has Script or AgentTemplate files.
Routing
Local config directory not initialized
If the user doesn't have a configs/ directory set up yet, route to the manage-configs skill first. That skill owns archagent init --enable-configs, local file layout, and the sync/deploy workflow.
User wants to author or modify agent configs
-
Start from CLI-backed templates, not memory:
- For new config objects, use:
archagent describe configsample <Kind> - For Script configs, always use:
The script docs are the live source of truth. Do not invent or paraphrase the language from memory.archagent describe scriptdocs archagent describe configsample Script
- For new config objects, use:
-
Use the standard config-driven model:
- Script logic lives in
kind: Scriptconfigs. - Agent behavior lives in an
AgentTemplate. - Custom tools should use
kind: custom,handler_type: script, andconfig_refpointing at Script configs. - When creating configs outside a project directory, use
-fto read from a file:archagent create config -k AgentTemplate -f configs/agents/my-agent.yaml
- Script logic lives in
-
Validate early:
archagent validate config -k <Kind> -f <path>Run validation before deploy whenever the user changes Script or template files.
-
Deploy through the normal flow after authoring:
- If the agent has Script configs or other supporting files, sync them first:
This pushes local config files (Scripts, templates) but does not create agents. Skip this step if the agent only has a single AgentTemplate file —archagent deploy configsdeploy agenthandles its own config upload. - Then provision the agent from its template:
This uploads the template config and creates the agent with its routines, tools, and installations.archagent deploy agent <yaml-file> - Important:
deploy configsanddeploy agentare different commands. Usedeploy configsto sync a directory of config files; usedeploy agentto create an agent from a template.
- If the agent has Script configs or other supporting files, sync them first:
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 · 122 lines · 72 tokens per session scan A cd3a7e614d52
archagent-author-agent is a skill published in the GitHub repository ArchAstro/archagents (5 stars, last pushed 3d ago), licensed MIT. It adds 72 tokens to every session and 1,166 once invoked, about $0.0004 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
test-review
You are an expert DataHub test reviewer. Your role is to evaluate pytest smoke tests against established testing standards, identify issues, and provide actionable feedback.
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.
docx
Read, create, and convert Microsoft Word (.docx) documents — extract text and tables, build reports from markdown/JSON, and export to PDF.