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 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/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/archastro/archagents/archagent-author-agent"><img src="https://agentmods.dev/badge/skills/archastro/archagents/archagent-author-agent.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00072 | $0.01166 |
| Opus 5.5 | $0.00029 | $0.00466 |
| Sonnet 5.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 2mo 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.
- 2mo 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 (7 stars, last pushed 29d ago), licensed MIT. It adds 72 tokens to every session and 1,166 once invoked, about $0.0003 per session on Opus 5.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.
sre-agent
Deploy or update the SRE Agent on Omnara, a production investigator that diagnoses issues across AWS and source code and reports the likely cause with evidence. Use when the user asks to deploy, set up, update, or remove the SRE agent.
browser-agent
Build and deploy a Browser Agent on Omnara, a long-running agent that signs in to web apps with stored credentials and works in a real browser, overnight if needed. Interviews the user about the job, sign-ins, schedule, and Slack or Discord first. Use when the user asks to build, deploy, set up, update, or remove a…
email-agent
Deploy or update the Email Agent on Omnara, an agent with its own email address that people can email, Cc, or @mention, built on Primitive's hosted email functions and MCP server. Use when the user asks to deploy, set up, update, customize, or remove the email agent.
linkedin-signal-agent
Deploy or update the LinkedIn Signal Agent on Omnara, an agent that scrapes LinkedIn posts (keyword search plus tracked company and profile feeds) and delivers a daily digest. Use when the user asks to deploy, set up, update, or remove the LinkedIn signal agent.
posthog-analytics-agent
Deploy or update the PostHog Analytics Agent on Omnara, an agent that queries a PostHog project through PostHog's MCP server and delivers a daily usage report. Use when the user asks to deploy, set up, update, or remove the PostHog analytics agent.