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-integration-patternsgit 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-integration-patterns)<a href="https://agentmods.dev/skills/archastro/archagents/archagent-integration-patterns"><img src="https://agentmods.dev/badge/skills/archastro/archagents/archagent-integration-patterns/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-integration-patterns"><img src="https://agentmods.dev/badge/skills/archastro/archagents/archagent-integration-patterns.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.00082 | $0.01325 |
| Opus 5.5 | $0.00033 | $0.00530 |
| Sonnet 5.5 | $0.00016 | $0.00265 |
| Haiku 4.5 | $0.00008 | $0.00133 |
Grade A, and why
archagent-integration-patterns 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Patterns
Most customer integrations collapse to one of seven shapes. When a
customer describes what they want, map it to the closest pattern below
and produce the minimal agent.yaml snippet. Then load the deeper
skill (archagent-author-agent, archagent-build-script, archagent-build-workflow) to fill in
details.
Pattern 1 — GitHub PR review
Use when: customer wants to review PRs, triage issues, or react to pushes.
installations:
- kind: integration/github
config: {}
routines:
- name: review-prs
handler_type: preset
preset_name: do_task
event_type: webhook.github_app.pull_request
event_config:
webhook.github_app.pull_request:
filters: {}
status: active
Critical: GitHub sends multiple events per PR. Enforce
action in {"opened", "synchronize"} filter or in the identity
prompt, otherwise the agent reviews the same PR N times.
Reference sample: agents/code-review-agent in this repo.
Pattern 2 — Slack bot
Use when: the customer's users should talk to the agent in Slack.
Install the Slack app installation. The simplest shape uses
thread.session.join + the participate preset — Slack messages get
proxied into threads automatically.
installations:
- kind: archastro/thread
config: {}
- kind: integration/slack
config: {}
routines:
- name: participate-slack
handler_type: preset
preset_name: participate
event_type: thread.session.join
event_config:
thread.session.join:
filters: {}
To post outbound (from scripts/workflows), use the slack script
namespace: let slack = import("slack"); unwrap(slack.post_message(...)).
Pattern 3 — Scheduled job
Use when: "run every Monday at 9am", "check this feed every hour".
routines:
- name: weekly-digest
handler_type: preset
preset_name: do_task
event_type: schedule.cron
schedule: "0 9 * * 1"
event_config:
schedule.cron:
filters: {}
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 · 188 lines · 82 tokens per session scan A 6b3de4c9908b
archagent-integration-patterns is a skill published in the GitHub repository ArchAstro/archagents (7 stars, last pushed 29d ago), licensed MIT. It adds 82 tokens to every session and 1,325 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.