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 DekaPrayoga/AurixAgent --skill architecture-decision-recordsgit clone --depth 1 https://github.com/DekaPrayoga/AurixAgentWrote 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/dekaprayoga/aurixagent/architecture-decision-records)<a href="https://agentmods.dev/skills/dekaprayoga/aurixagent/architecture-decision-records"><img src="https://agentmods.dev/badge/skills/dekaprayoga/aurixagent/architecture-decision-records/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/dekaprayoga/aurixagent/architecture-decision-records"><img src="https://agentmods.dev/badge/skills/dekaprayoga/aurixagent/architecture-decision-records.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.00055 | $0.01634 |
| Opus 5 | $0.00028 | $0.00817 |
| Sonnet 5 | $0.00011 | $0.00327 |
| Haiku 4.5 | $0.00006 | $0.00163 |
Grade A, and why
architecture-decision-records 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 6d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 6d ago First seen · 180 lines · 55 tokens per session scan A b4d9113e115a
architecture-decision-records is a skill published in the GitHub repository DekaPrayoga/AurixAgent (63 stars, last pushed 1mo ago), with no licence file. It adds 55 tokens to every session and 1,634 once invoked, about $0.0003 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-03.
Other skills, from other repositories
code-agent
Use when implementing features from specs — reads requirements, writes code with tests, iterates until verification passes.
deploy-agent
Use when ship code through controlled pipeline with verification gates and rollback plans.
planning-agent
Use when decompose complex tasks into executable steps with dependencies, risk assessment, and verification criteria.
research-agent
Use when investigating topics deeply with cross-referenced sources and producing evidence-backed findings.
review-agent
Use when reading code changes with adversarial intent to find bugs, security holes, logic errors, and performance traps.
autonomous
Use when five specialized autonomous agents (code, deploy, planning, research, review) working as a coordinated pipeline. From spec to shipped code with automated planning, research, review, and deployment gates. Use when working with autonomous agents.