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/agent-engineer-master/skill-engineer/audit-brandnpx skills add Agent-Engineer-Master/skill-engineer --skill audit-brandgit clone --depth 1 https://github.com/Agent-Engineer-Master/skill-engineerWrote 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/agent-engineer-master/skill-engineer/audit-brand)<a href="https://agentmods.dev/skills/agent-engineer-master/skill-engineer/audit-brand"><img src="https://agentmods.dev/badge/skills/agent-engineer-master/skill-engineer/audit-brand.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 | $0.00111 | $0.02920 |
| Opus 5 | $0.00056 | $0.01460 |
| Sonnet 5 | $0.00022 | $0.00584 |
| Haiku 4.5 | $0.00011 | $0.00292 |
Grade A, and why
audit-brand 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 4d 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 — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit-brand — Brand Positioning Audit & Evolution
Audit brand consistency, refresh positioning, and develop messaging frameworks for an existing brand.
Usage:
/audit-brand personal-brand— full audit of personal brand/audit-brand dtc-store— full audit of DTC store brand/audit-brand personal-brand voice— voice-only audit/audit-brand dtc-store positioning— positioning-only refresh
Overview
5 audit modules that can run independently or as a full suite. Each module produces a scorecard section and specific recommendations.
| Module | What It Checks | Output |
|---|---|---|
| 1. Positioning | Is positioning still differentiated? Has competition shifted? | Positioning scorecard + refresh recommendations |
| 2. Voice | Does content match voice guidelines? Drift detection. | Voice consistency score + specific fixes |
| 3. Visual | Do visual touchpoints match brand guidelines? | Visual consistency checklist |
| 4. Pillars | Are content pillars still resonating? Any gaps or drift? | Pillar health report |
| 5. Coherence | Wolff Olins 3-pillar check: behavior + communication + design aligned? | Overall coherence verdict |
Full audit: Run all 5 modules sequentially, present combined scorecard. Focused audit: Run only the specified module(s).
Step 0 — Load Context and Identify Brand
Determine which brand from the argument. If ambiguous, ask.
personal-brand:
- Read your brand summary file — current state, pillars, thesis
- Read your LinkedIn voice guidelines file
- Read your X/social voice guidelines file (if it exists)
- Read your founder/about-me context file
- Read your anti-goals or what-to-avoid file
- Glob your recent published posts directory — scan the 5 most recent
dtc-store:
- Read your store state/context file — current store state
- Read your brand guidelines file (if missing, stop: "No brand guidelines found. Run /build-brand first.")
- Read any recent brand strategy notes or memory files
What ships with it
4 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.
- 4d ago First seen · 337 lines · 111 tokens per session scan A 1666295625e1
audit-brand is a skill published in the GitHub repository Agent-Engineer-Master/skill-engineer (8 stars, last pushed 1mo ago), licensed MIT. It adds 111 tokens to every session and 2,920 once invoked, about $0.0006 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
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
extract
Run the full Semantica semantic extraction pipeline on a file or selected text — NER, relations, events, coreference resolution, triplets, and validation. Clears result cache before each run. Returns Markdown tables with entity/relation/event/triplet results and inline validator warnings.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
kayba-stage-7-fixer
Implement the approved fixes from the action plan and log all changes. Trigger when the user says "run stage 7", "implement fixes", "apply action plan", or when invoked by the kayba-pipeline orchestrator. Requires eval/actionplan.md to exist.