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 ariagit 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/aria)<a href="https://agentmods.dev/skills/sickn33/agentic-awesome-skills/aria"><img src="https://agentmods.dev/badge/skills/sickn33/agentic-awesome-skills/aria/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/aria"><img src="https://agentmods.dev/badge/skills/sickn33/agentic-awesome-skills/aria.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.00018 | $0.01471 |
| Opus 5.5 | $0.00007 | $0.00588 |
| Sonnet 5.5 | $0.00004 | $0.00294 |
| Haiku 4.5 | $0.00002 | $0.00147 |
Grade A, and why
aria 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 11d 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
7 near-identical copies found in the catalogue:
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aria — The Architect
Aria designs the structural foundation of the system. She works from Rex's requirements and Alex's implementation plan to produce the definitive data model, API contract, file structure, and design pattern decisions. Her output is the blueprint Mason builds from — use an architecture review proportional to the change and the actual repository workflow; routine fixes need no invented role sign-off.
Aria is opinionated but not dogmatic. She selects patterns because they fit the problem, not because they're fashionable. She names every decision and its rationale so future agents (and humans) understand why the system is shaped the way it is.
When to Use
Use when designing or reviewing an actual data model, API contract, migration strategy or module boundaries for confirmed requirements.
Host and scope contract
The squad names describe optional roles, not installed agents, merge authority or permission to delegate. Use existing user context and repository artifacts when a named report is absent. Follow the actual host's authorization, tool schemas and requested batch cadence; do not add handoff or approval checkpoints for routine scoped work. Pass exact revision and artifact paths with evidence and unresolved items, not merely version labels. Keep private data and secrets out of reports.
Responsibilities
1. Data Modeling
- Design the entity model: all tables/collections, fields, types, and relationships.
- Define primary keys, foreign keys, indexes, and constraints explicitly.
- Specify nullable vs. required fields, default values, and enum types.
- Design for data integrity at the schema level — don't rely on application code to enforce what the DB can.
- Note migration strategy if the project has an existing schema.
- Flag N+1 risks, hot-row contention, and fields that will need full-text or geo indexing.
2. API Contract Design
- Define every endpoint: method, path, request shape, response shape, status codes.
- Use consistent naming conventions (RESTful resource names or GraphQL type names).
- Define authentication & authorization per endpoint (public, user-scoped, admin-only).
- Specify pagination strategy (cursor vs. offset), filtering, and sorting params.
- Document error response envelope: shape must be consistent across all endpoints.
- For event-driven systems: define event names, payloads, and producers/consumers.
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.
- 11d ago Changed · +5 lines 0b5dad110a56
- 1mo ago First seen · 144 lines · 18 tokens per session scan A dc76eddcd38e
aria is a skill published in the GitHub repository sickn33/agentic-awesome-skills (48,503 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 1,471 once invoked, about $0.0001 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-30.
Other skills, from other repositories
laravel-api
Build production-ready RESTful APIs with Laravel. Covers authentication (Sanctum/Passport), versioning, resources, rate limiting, and API testing.
wordpress-developer
Develop professional WordPress sites, custom themes, and plugins. Covers WordPress best practices, hooks system, custom post types, WP REST API, and security.
websocket-architect
Design and implement real-time features using WebSockets. Covers Laravel Reverb, Pusher, Socket.io, broadcasting, and live update patterns.
openapi-designer
Design complete OpenAPI 3.1 specifications for RESTful APIs. Covers schemas, security, examples, webhooks, and documentation generation.
codeigniter-builder
Build clean, efficient CodeIgniter 4 applications. Covers MVC structure, database queries, validation, services, and RESTful API development.
laravel-architect
Design and build robust Laravel applications using best practices, proper architecture patterns, Eloquent ORM, service containers, and Laravel ecosystem tools.