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 agentmods add skills/nockasdd/domyh-awf-code/angularnpx skills add nockasdd/domyh-awf-code --skill angulargit clone --depth 1 https://github.com/nockasdd/domyh-awf-codeWhat 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 | $0.00023 | $0.01775 |
| Opus 5 | $0.00012 | $0.00888 |
| Sonnet 5 | $0.00005 | $0.00355 |
| Haiku 4.5 | $0.00002 | $0.00178 |
Grade A, and why
angular 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 2d 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 ships with it
5 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.
- 2d ago First seen · 318 lines · 23 tokens per session scan A b49c633a47df
angular is a skill published in the GitHub repository nockasdd/domyh-awf-code (2 stars, last pushed 14d ago), with no licence file. It adds 23 tokens to every session and 1,775 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
methodology-curator
Surface expert frameworks. Use when creating or evaluating skills, hooks, or agents.
product-architect
Complete product development system with 64 agents and 35 frameworks. Use when the user wants to build a product, write a PRD, plan an MVP or roadmap, design an app, research a market or check whether a feature already exists or is novel, do competitive analysis, run a security audit, build a financial model, plan…
astro
Use when building a content-driven or marketing site with Astro 6: static-first pages, islands and partial hydration, content collections, server islands, per-route on-demand rendering, deploy adapters, and Astro 5→6 migration. NOT app-router React with server actions and heavy client interactivity (that is nextjs).
deck-pipeline
Multi-agent pipeline that builds a polished presentation deck from a single topic. Four agents work in sequence — Strategist defines the narrative, Builder creates the deck, Critic reviews it like a McKinsey EM, Fixer applies the top fixes. Use when you need a presentation that survives senior audiences.
stakeholder-map
Map the people who can make or break a decision onto a Power/Interest grid, with each named stakeholder's stance (champion / skeptic / blocker / unknown), what they care about, and the single influence move you'll make for them. Use before any cross-functional decision, big launch, reorg, or executive ask — anywhere…
top-down-memo
Answer-first writing using the Minto Pyramid Principle. Lead with the conclusion, then 2–4 MECE supporting arguments, then evidence under each. Use whenever you have a recommendation, finding, or assessment to communicate in writing — memos, emails to execs, Slack updates that need to land, briefing docs. Different…