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-installgit 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-install)<a href="https://agentmods.dev/skills/gigayaya/daa-master/daa-install"><img src="https://agentmods.dev/badge/skills/gigayaya/daa-master/daa-install.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.00037 | $0.01223 |
| Opus 5 | $0.00018 | $0.00611 |
| Sonnet 5 | $0.00007 | $0.00245 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade A, and why
daa-install 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DAA Project Installer
Overview
This skill installs DAA (Declarative Action Architecture) rules and conventions into the user's current project. It creates a knowledge base directory for on-demand reference and updates existing configuration files to point agents to those rules.
What Gets Installed
| Target | Action | Content |
|---|---|---|
docs/daa_rules/ |
Created (always) | 7 knowledge base files covering DAA principles, naming, anti-patterns, code generation, code review, and project structure |
CLAUDE.md |
Modified (only if exists) | Minimal DAA section with pointer table to docs/daa_rules/ |
AGENTS.md |
Modified (only if exists) | Minimal DAA section with pointer table to docs/daa_rules/ |
README.md |
Modified (only if exists) | Brief DAA architecture section |
Installation Procedure
Follow these steps IN ORDER. Do not skip steps.
Step 1: Safety Check
Determine the user's current working directory. This is the project where DAA will be installed.
STOP if the current directory is inside the DAA plugin repository itself (contains plugins/DAA-Master/skills/). Warn the user: "This skill should be invoked from your own project, not the DAA plugin repo."
Step 2: Survey Existing Files
Check which of these files exist in the project root:
CLAUDE.mdAGENTS.mdREADME.mddocs/daa_rules/directory
For each existing file, check if it already contains the marker <!-- DAA:BEGIN. This determines whether this is a fresh install or an update.
Step 3: Show Installation Plan
Before making any changes, tell the user exactly what will be done:
Always created/updated:
docs/daa_rules/— 7 knowledge base files (overwritten if they exist)
Only if the file exists:
- For each of CLAUDE.md, AGENTS.md, README.md:
- File exists + no DAA marker → APPEND DAA section
- File exists + DAA marker found → REFRESH (replace DAA block with latest)
- File does not exist → SKIP (report to user)
What ships with it
10 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.
- templates/agents-md-section.md 1.1 KB
- templates/claude-md-section.md 1.1 KB
- templates/docs-daa-rules/anti-patterns.md 5.4 KB
- templates/docs-daa-rules/code-generation-rules.md 8.0 KB
- templates/docs-daa-rules/code-review-checklist.md 6.8 KB
- templates/docs-daa-rules/core-principles.md 5.4 KB
- templates/docs-daa-rules/naming-conventions.md 3.4 KB
- templates/docs-daa-rules/project-structure.md 7.8 KB
- templates/docs-daa-rules/README.md 1.2 KB
- templates/readme-md-section.md 852 B
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 · 111 lines · 37 tokens per session scan A d6302368d403
daa-install is a skill published in the GitHub repository gigayaya/DAA-Master (1 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,223 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-08-31.
Other skills, from other repositories
run-smoke-tests
Inspect an unfamiliar repository, interpret a broad Markdown user journey at runtime, operate the real product through its supported web, API, CLI, desktop, or mobile surface, and produce an auditable pass, fail, or blocked judgment with screenshots, logs, recordings, and a step timeline when available. Use when asked…
test-review
A review checklist for newly written or changed automated tests using TypeScript and Playwright. Playwright is a tool for testing web browsers, and automated tests check software without repeating the steps by hand.
test-strategy-document
Create a production-ready Testing Strategy and QA Execution Plan. Covers testing levels (unit, integration, E2E, performance), mocking boundaries, test environment matrix, code coverage thresholds, and automated CI pipeline runsheets. Use when establishing a QA framework for a new system or feature set.
xcode-testing-workflow
Guide Swift Testing, XCTest, XCUITest, XCUIAutomation-oriented mechanics, code coverage, xctestplan matrices, accessibility-verification follow-through, test filtering, retries, diagnostics, and test-specific fallback work in existing Xcode-managed projects and workspaces. Use when Xcode-aware execution is needed and…
evaluating-as-user
Evaluates software quality from an end user's perspective. Use when emulating a real user to assess a running web app, CLI tool, or API.
test-selection
Use this skill when someone describes a specific code path, feature, or bug and asks what kind of test to write for it — or when an audit or strategy engagement surfaces a testing gap and needs a recommendation for where to start. Trigger on "what test should I write for this", "unit or integration test for X", "our…