AAS Core is a local control plane for coding agents that lets them search a large catalogue of skills, choose a stack, validate it, and create a reproducible plan. It is used to assemble and review agent workflows through its CLI, local MCP server, catalogue, plugins, and Workbench. The catalogue add-ons provide the skills, plugins, bundles, and workflows that AAS Core helps agents select and validate.
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 sickn33/agentic-awesome-skills --skill automated-triagegit clone --depth 1 https://github.com/sickn33/agentic-awesome-skillsWrote 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/sickn33/agentic-awesome-skills/automated-triage)<a href="https://agentmods.dev/skills/sickn33/agentic-awesome-skills/automated-triage"><img src="https://agentmods.dev/badge/skills/sickn33/agentic-awesome-skills/automated-triage/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/sickn33/agentic-awesome-skills/automated-triage"><img src="https://agentmods.dev/badge/skills/sickn33/agentic-awesome-skills/automated-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
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.00042 | $0.02721 |
| Opus 5 | $0.00021 | $0.01360 |
| Sonnet 5 | $0.00008 | $0.00544 |
| Haiku 4.5 | $0.00004 | $0.00272 |
Grade A, and why
automated-triage 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 4d 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
4 near-identical copies found in the catalogue:
- automated-triage — 100% identical, 6 lines differ
- automated-triage — 100% identical, 6 lines differ
- automated-triage — 98% identical, 8 lines differ
- automated-triage — 98% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monte Carlo Automated Triage
This skill helps you design, test, and deploy an automated triage agent for Monte Carlo alerts. Rather than a fixed workflow, it gives you the building blocks — a set of MCP tools, a description of each triage stage, and a working example — so you can build a process that matches how your team actually responds to alerts.
Monte Carlo tool routing (required): Always call Monte Carlo MCP tools through this plugin's bundled server, whose fully-qualified tool names are
mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__<tool>(e.g.mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__get_alerts). Bare tool names used in this skill (get_alerts,search,get_table, …) refer to that bundled server. If the session also has a separately-configuredmonte-carlo-mcpserver, do not route to it — it may point at a different endpoint or credentials.
Read the reference files before proceeding:
- Triage stages and customisation:
references/triage-stages.md(relative to this file) - Working example workflow:
references/triage-example.md(relative to this file)
When to activate this skill
Activate when the user:
- Wants to triage or investigate recent Monte Carlo alerts (interactively or automated)
- Wants to set up automated triage for Monte Carlo alerts
- Asks to run agentic triage or investigate recent alert activity
- Wants to understand what triage tools are available and how to use them
- Is building or refining a triage prompt for their environment
- Wants to move from manual alert review to automated or semi-automated triage
When NOT to activate this skill
Do not activate when the user is:
- Investigating a specific known incident (help them directly)
- Creating or configuring monitors (use the monitoring-advisor skill)
- Running impact analysis before a code change (use the prevent skill)
Available MCP tools
All tools are available via the monte-carlo-mcp MCP server.
| Tool | Toolset | Purpose |
|---|---|---|
get_alerts |
default | Fetch recent alerts for a time window |
alert_assessment |
default | Score an alert by incident likelihood and potential impact (HIGH/MEDIUM/LOW each) |
run_troubleshooting_agent |
default | Run the Monte Carlo Troubleshooting Agent on a single alert; async by default — returns immediately, reuses existing results when available |
get_troubleshooting_agent_results |
default | Poll an async troubleshooting run by incident_id; returns status (not_found/running/success/failed) and results when complete |
update_alert |
default | Update an alert's status and/or declare an incident by setting severity |
set_alert_owner |
default | Assign an owner to an alert by email |
create_or_update_alert_comment |
default | Post or update a triage comment on an alert |
mark_event_as_normal |
default | Mark all anomaly events in an alert as normal, triggering ML threshold recalibration to prevent re-alerting on the same pattern |
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.
- 4d ago Changed · +6 lines f436eca23e46
- 7d ago First seen · 190 lines · 42 tokens per session scan A f52338ed1173
automated-triage is a skill published in the GitHub repository sickn33/agentic-awesome-skills (46,288 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 2,721 once invoked, about $0.0002 per session on Opus 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-09-05.
Other skills, from other repositories
build-nitro-modules
Builds React Native Nitro Modules from scratch in a monorepo. Scaffolds with Nitrogen, authors HybridObject TypeScript specs, generates native boilerplate, implements in C++/Swift/Kotlin, wires an example app, and prepares for npm publishing. Use when creating a new Nitro Module, implementing native functionality via…
flutter-developer
Build beautiful, performant Flutter applications for iOS, Android, and web. Covers state management, navigation, animations, platform channels, and deployment.
laravel-api
Build production-ready RESTful APIs with Laravel. Covers authentication (Sanctum/Passport), versioning, resources, rate limiting, and API testing.
laravel-architect
Design and build robust Laravel applications using best practices, proper architecture patterns, Eloquent ORM, service containers, and Laravel ecosystem tools.
wordpress-developer
Develop professional WordPress sites, custom themes, and plugins. Covers WordPress best practices, hooks system, custom post types, WP REST API, and security.
redis-master
Leverage Redis for caching, sessions, pub/sub, queues, rate limiting, and real-time features. Design Redis data structures for optimal performance.