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 gigayaya/DAA-Master --skill daa-architectgit clone --depth 1 https://github.com/gigayaya/DAA-MasterWrote 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/gigayaya/daa-master/daa-architect)<a href="https://agentmods.dev/skills/gigayaya/daa-master/daa-architect"><img src="https://agentmods.dev/badge/skills/gigayaya/daa-master/daa-architect.svg" alt="Measured on agentmods" 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.00026 | $0.01036 |
| Opus 5 | $0.00013 | $0.00518 |
| Sonnet 5 | $0.00005 | $0.00207 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
daa-architect 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 8d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DAA Framework Architect
REQUIRED BACKGROUND: You MUST understand daa:daa-core before using this skill.
Overview
Use this skill when starting a new E2E automation project, restructuring an existing test suite, or scaling an automation framework. It provides project structure templates and advanced patterns for growing test suites.
When to Use
- New project: Scaffolding directory structure for a DAA-compliant framework
- Migration: Converting POM or flat scripts to DAA three-layer architecture
- Scaling: Test suite growing from 50 → 500+ scenarios; need structured abstraction
Project Scaffold
A DAA-compliant project separates the three layers in the directory structure:
project/
├── lib/ # Framework code (Action + Physical layers)
│ ├── api/ # API testing support
│ │ ├── action_layer.py # Action Layer: API business actions
│ │ └── physical_layer.py # Physical Layer: HTTP client wrapper
│ ├── web/ # Web/UI testing support
│ │ ├── action_layer.py # Action Layer: UI business actions
│ │ ├── physical_layer.py # Physical Layer: browser driver wrapper
│ │ └── constants.py # UI selectors and URLs
│ └── __init__.py
├── tests/ # Test Layer
│ ├── api/
│ │ ├── test_crud.py # API test scenarios
│ │ └── test_workflows.py # API composite workflow tests
│ ├── web/
│ │ └── test_search.py # Web test scenarios
│ └── conftest.py # Test fixtures and configuration
├── config/ # Environment configuration
├── requirements.txt # Dependencies
└── README.md
→ Full template with explanations: project-scaffold.md
Scaling Decision Tree
When Action Layer complexity grows, apply the appropriate design pattern:
digraph scaling {
rankdir=TB;
"Action Layer growing complex?" [shape=diamond];
"Too many parameters?" [shape=diamond];
"API interface mismatch?" [shape=diamond];
"If/else branching?" [shape=diamond];
"Sequential pipeline?" [shape=diamond];
"Apply Builder Pattern" [shape=box];
"Apply Adapter Pattern" [shape=box];
"Apply Strategy Pattern" [shape=box];
"Apply Chain Pattern" [shape=box];
"Extract Composite Action" [shape=box];
"Action Layer growing complex?" -> "Too many parameters?" [label="yes"];
"Action Layer growing complex?" -> "Extract Composite Action" [label="no, just repetition"];
"Too many parameters?" -> "Apply Builder Pattern" [label="yes"];
"Too many parameters?" -> "API interface mismatch?" [label="no"];
"API interface mismatch?" -> "Apply Adapter Pattern" [label="yes"];
"API interface mismatch?" -> "If/else branching?" [label="no"];
"If/else branching?" -> "Apply Strategy Pattern" [label="yes"];
"If/else branching?" -> "Sequential pipeline?" [label="no"];
"Sequential pipeline?" -> "Apply Chain Pattern" [label="yes"];
}
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 101 lines · 26 tokens per session scan A 50fe1bbd1297
daa-architect is a skill published in the GitHub repository gigayaya/DAA-Master (1 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 1,036 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
phx-work
Execute Elixir/Phoenix plan tasks with progress tracking. Use after phx-plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.
lab:autoresearch
Self-improving loop for plugin skills. Reads program.md, proposes one mutation per iteration, evaluates against deterministic scorer, keeps improvements via git, reverts failures. Targets weakest skill+dimension. Use with /loop for overnight runs.
codex-loop
Fix Elixir/Phoenix code until Codex CLI review comes back clean — bounded review, fix, verify loop before opening a PR. Use when codex is installed and you want an external cross-model critic on your changes before pushing.
verify
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.
codex-ab
Run an A/B codex review experiment — holistic codex review vs 3 focused dimension passes (security, ecto, liveview) on the branch diff, classify findings, report a panel-value verdict. Use when the branch is fresh, before any codex review runs.
mix-compression
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.