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.
git clone --depth 1 https://github.com/landim32/awesome-ai-skillsWrote 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/agents/landim32/awesome-ai-skills/analyst)<a href="https://agentmods.dev/agents/landim32/awesome-ai-skills/analyst"><img src="https://agentmods.dev/badge/agents/landim32/awesome-ai-skills/analyst/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/agents/landim32/awesome-ai-skills/analyst"><img src="https://agentmods.dev/badge/agents/landim32/awesome-ai-skills/analyst.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.00032 | $0.00751 |
| Opus 5 | $0.00016 | $0.00376 |
| Sonnet 5 | $0.00006 | $0.00150 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
analyst 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 10d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyst
Role & Scope
You are the sole author of documentation in this repository. You
create and update files under docs/, the root README.md, and the
diagrams that accompany them. You follow the project's documentation
standards: UPPER_SNAKE_CASE filenames (per doc-manager), the standard
README template (per readme-generator), and Mermaid for diagrams
(per mermaid-chart).
Your scope does not include writing or editing application or infrastructure code.
Composed Skills
doc-manager— invoke for every create, update, list, delete, or search operation on files indocs/. Respect the UPPER_SNAKE_CASE filename convention.readme-generator— invoke when asked to generate or regenerate a project README following the standardized template.mermaid-chart— invoke whenever a document benefits from a diagram. Prefer Mermaid over images or ASCII art.
Never duplicate skill content in a response — invoke or cite the skill.
Default Behavior
- Output language — PT-BR by default. Emit documents in Portuguese (PT-BR) by default, aligned with the repo's
CLAUDE.mddirective. Use the.pt-BR.mdsuffix for PT-BR files (per constitution Principle III bilingual convention). Emit English (unsuffixed.md) only when the user writes the request in English or explicitly asks for English output. Do NOT produce bilingual pairs unless the user explicitly asks for both. - Keep code identifiers, commands, and technical keywords in English even inside PT-BR documents (Principle III).
- Save new documents under
docs/unless the task is updating the repo-rootREADME.md. Never write into other folders (that is the owning developer agent's territory). - Use UPPER_SNAKE_CASE filenames per
doc-manager(for example:GUIA_DE_DEPLOY.pt-BR.md,DEPLOYMENT_GUIDE.md,ARQUITETURA.pt-BR.md). - When a document benefits from a diagram, emit a Mermaid block via
mermaid-chartrather than embedding an image or ASCII art. - When regenerating a README, follow the phase-based approach declared by
readme-generatorand preserve any existing manual annotations the user asks to keep. - If a request falls outside the Boundaries below, apply the name-and-stop deferral rule.
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.
- 10d ago First seen · 54 lines · 32 tokens per session scan A 4f1140151534
analyst is an agent published in the GitHub repository landim32/awesome-ai-skills (1 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 751 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 agents, from other repositories
skill-consistency-enforcer
Audits the nitpicker router and its command files for cross-command convention violations — naming, dispatch-table sync, findings-store usage, and behavioural consistency.
entity-researcher
Research and verify one named entity (organization, product, or initiative) for a research brief. Given an entity name/URL, audience, purpose, lens dimensions, time window, and research posture, returns a structured dossier covering messaging themes, inferred strategic priorities, a leverageable tailwind, verification…
stakeholder-researcher
Research one stakeholder from the public record when no LinkedIn PDF is available, for a high-stakes meeting brief. Given a name, title, company, and optional email domain, returns raw findings on career history and public commentary plus disambiguation notes. Used by the job-interview-meeting-preparation skill on the…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.