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-troubleshootinggit 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-troubleshooting)<a href="https://agentmods.dev/skills/archastro/archagents/archagent-troubleshooting"><img src="https://agentmods.dev/badge/skills/archastro/archagents/archagent-troubleshooting/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-troubleshooting"><img src="https://agentmods.dev/badge/skills/archastro/archagents/archagent-troubleshooting.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.00073 | $0.01235 |
| Opus 5.5 | $0.00029 | $0.00494 |
| Sonnet 5.5 | $0.00015 | $0.00247 |
| Haiku 4.5 | $0.00007 | $0.00123 |
Grade A, and why
archagent-troubleshooting 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ArchAgents Troubleshooting
When something is broken, diagnose in this order. Most issues resolve in the first three steps.
Step 1 — Check auth and CLI state
archagent auth status
archagent --version
Common findings:
Status: Expired→archagent auth login <email>- CLI errors about version skew → reinstall via the
archagent-installskill. - Wrong app selected →
archagent auth app listandarchagent auth app set <id>.
Step 2 — Validate configs before assuming deploy succeeded
archagent validate config -k AgentTemplate -f agent.yaml
archagent validate config -k Script -f scripts/foo.aascript
Validation errors surface the exact field that failed. Fix locally, re-validate, then redeploy. Do not trust that a deploy succeeded just because the CLI exited 0 — validate explicitly.
Step 3 — Confirm server state matches local
archagent describe agent <agent-key>
archagent describe config -k Script <script-slug>
If the server version is older than what you expect, the last
archagent deploy configs / deploy agent did not include the file.
Re-run the deploy. If the server version is newer than local, pull:
archagent sync configs
Common symptoms and fixes
"The agent didn't respond in the thread"
- Is there a
thread.session.joinroutine withpreset: participate? Without it, the agent sits silent. - Is the agent installed in the thread? Check
archagent list threadmembers --thread <id>. - Does the routine have
status: active?
"The scheduled routine didn't fire"
- Both
schedule: "<cron>"andevent_type: schedule.cronmust be set at the routine level. The most common bug is putting the schedule underevent_config.schedule, where it is silently ignored. - Timezone: cron runs in UTC. "9am Monday" is
0 9 * * 1UTC, not your local 9am. archagent list routineexecutions --routine <id>shows whether it fired.
"The webhook routine didn't fire"
- The webhook URL — copy it from
archagent describe routine <id>. There is exactly one per routine; do not guess it. archagent list routineexecutionsshows inbound requests even when the handler errors. If there is no execution record, the webhook never reached the platform.- Filters: an overly narrow
filtersblock can drop the event. Start withfilters: {}and narrow once it works.
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 · 142 lines · 73 tokens per session scan A 2527e54207ea
archagent-troubleshooting is a skill published in the GitHub repository ArchAstro/archagents (7 stars, last pushed 29d ago), licensed MIT. It adds 73 tokens to every session and 1,235 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
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.
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.