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 deploy-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/deploy-agent)<a href="https://agentmods.dev/skills/archastro/archagents/deploy-agent"><img src="https://agentmods.dev/badge/skills/archastro/archagents/deploy-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/deploy-agent"><img src="https://agentmods.dev/badge/skills/archastro/archagents/deploy-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.00070 | $0.00947 |
| Opus 5.5 | $0.00028 | $0.00379 |
| Sonnet 5.5 | $0.00014 | $0.00189 |
| Haiku 4.5 | $0.00007 | $0.00095 |
Grade A, and why
deploy-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- archagent-deploy-agent — 86% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ArchAstro Agent Deployment
Deploy an agent from a YAML template and get it running in a thread.
This skill assumes the ArchAgent CLI is already installed and authenticated. Use the /archagents:install and /archagents:auth commands in this same plugin instead of trying to install or authenticate the CLI manually inside this skill.
Always Start with State
Every invocation must begin by understanding what already exists:
archagent auth status
archagent list agents
If the user is working from a local repo, also inspect whether a configs/ directory already exists. Determine whether they want to:
- deploy a new config-driven agent,
- redeploy an existing template,
- or work with an existing running agent.
Routing
Local config directory not initialized
If the user has config files but no configs/ directory set up, route to the manage-configs skill first. That skill owns local config management.
User wants to deploy a new agent
Use the config-driven golden path. Do not skip straight to create agent.
-
Deploy configs first:
archagent deploy configsThis pushes Script and AgentTemplate configs to the server. For config-driven agents, this should happen before provisioning the agent itself.
-
Deploy the agent from the template file:
archagent deploy agent <yaml-file>This creates the full agent stack in one step: app config, agent record, routines, and installations. Note the agent ID (
agi_...) from the output.Important: Always use
deploy agent, notcreate agent. Thecreate agentcommand only creates the agent record without provisioning routines or installations. -
Verify the deployment:
archagent list agents -
Offer next steps: ask if the user wants to add the agent to a thread and start chatting. If yes, create a thread with members and hand off to the
chatskill.
User needs help creating or editing the config files first
Route to the author-agent skill before deploying. That skill owns:
AgentTemplateand Script config creationarchagent describe configsamplearchagent describe scriptdocs- routine scheduling shape
- env-var scope guidance
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 · 113 lines · 70 tokens per session scan A b16d34efd625
deploy-agent is a skill published in the GitHub repository ArchAstro/archagents (7 stars, last pushed 29d ago), licensed MIT. It adds 70 tokens to every session and 947 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.