Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ArchAstro/archagentsnpx agentmods add skills/archastro/archagents/manage-configsWrote 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/manage-configs)<a href="https://agentmods.dev/skills/archastro/archagents/manage-configs"><img src="https://agentmods.dev/badge/skills/archastro/archagents/manage-configs/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/manage-configs"><img src="https://agentmods.dev/badge/skills/archastro/archagents/manage-configs.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.00077 | $0.01797 |
| Opus 5.5 | $0.00031 | $0.00719 |
| Sonnet 5.5 | $0.00015 | $0.00359 |
| Haiku 4.5 | $0.00008 | $0.00180 |
Grade A, and why
manage-configs 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-manage-configs — 94% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ArchAstro Local Config Management
Set up and manage a local configs/ directory for editing agent configs as files, syncing with the server, and deploying changes.
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.
What is Local Config Management?
Instead of creating and editing configs one-by-one through CLI CRUD commands, you can manage them as local files in a configs/ directory. This enables:
- Edit configs in your editor with syntax highlighting and version control
- Batch deploy all changes in dependency order
- Sync server configs down to local files
- Browser editor for visual editing of individual configs
The CLI tracks the mapping between local files and server configs in a manifest file.
Always Start with State
Every invocation must begin by understanding the current project state:
archagent auth status
ls configs/ 2>/dev/null || echo "No configs directory"
Determine:
- Does a
configs/directory already exist? - Is the user starting a new project or working with an existing one?
- Do they want to pull configs from the server or push local changes?
Routing
User wants to set up a configs directory for the first time
-
Initialize the config directory:
archagent init --enable-configsThis enables local config management and creates the configured
configs/directory if needed. It does not automatically sync remote configs; usearchagent sync configsnext when you want local files. -
Explain the layout: After init, the directory looks like:
configs/ ├── .archastro-manifest.json # Maps local files to server configs (do not edit manually) ├── agents/ # AgentTemplate configs ├── skills/ # Skill bundles ├── scripts/ # Script configs ├── workflows/ # Workflow configs └── ... # Other config kinds
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 · 221 lines · 77 tokens per session scan A c40731018b2a
manage-configs is a skill published in the GitHub repository ArchAstro/archagents (7 stars, last pushed 29d ago), licensed MIT. It adds 77 tokens to every session and 1,797 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.