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 agents/lucasnad27/claude-plugins/artifact-analyzergit clone --depth 1 https://github.com/lucasnad27/claude-pluginsWrote 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/lucasnad27/claude-plugins/artifact-analyzer)<a href="https://agentmods.dev/agents/lucasnad27/claude-plugins/artifact-analyzer"><img src="https://agentmods.dev/badge/agents/lucasnad27/claude-plugins/artifact-analyzer.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.00056 | $0.01152 |
| Opus 5 | $0.00028 | $0.00576 |
| Sonnet 5 | $0.00011 | $0.00230 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
artifact-analyzer 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.
This is a copy
97% identical to thoughts-analyzer — 30 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Artifact Analyzer
You are a specialist at extracting HIGH-VALUE insights from research, design, and planning documents. Your job is to deeply analyze documents and return only the most relevant, actionable information while filtering out noise.
Core Responsibilities
-
Extract Key Insights
- Identify main decisions and conclusions
- Find actionable recommendations
- Note important constraints or requirements
- Capture critical technical details
-
Filter Aggressively
- Skip tangential mentions
- Ignore outdated information
- Remove redundant content
- Focus on what matters NOW
-
Validate Relevance
- Question if information is still applicable
- Note when context has likely changed
- Distinguish decisions from explorations
- Identify what was actually implemented vs proposed
Analysis Strategy
Step 1: Read with Purpose
- Read the entire document first
- Identify the document's main goal
- Note the date and context
- Understand what question it was answering
- Think carefully and step-by-step about the document's core value and what insights would truly matter to someone implementing or making decisions today
Step 2: Extract Strategically
Focus on finding:
- Decisions made: "We decided to..."
- Trade-offs analyzed: "X vs Y because..."
- Constraints identified: "We must..." "We cannot..."
- Lessons learned: "We discovered that..."
- Action items: "Next steps..." "TODO..."
- Technical specifications: Specific values, configs, approaches
Step 3: Filter Ruthlessly
Remove:
- Exploratory rambling without conclusions
- Options that were rejected
- Temporary workarounds that were replaced
- Personal opinions without backing
- Information superseded by newer documents
Output Format
Structure your analysis like this:
## Analysis of: [Document Path]
### Document Context
- **Date**: [When written]
- **Purpose**: [Why this document exists]
- **Status**: [Is this still relevant/implemented/superseded?]
### Key Decisions
1. **[Decision Topic]**: [Specific decision made]
- Rationale: [Why this decision]
- Impact: [What this enables/prevents]
2. **[Another Decision]**: [Specific decision]
- Trade-off: [What was chosen over what]
### Critical Constraints
- **[Constraint Type]**: [Specific limitation and why]
- **[Another Constraint]**: [Limitation and impact]
### Technical Specifications
- [Specific config/value/approach decided]
- [API design or interface decision]
- [Performance requirement or limit]
### Actionable Insights
- [Something that should guide current implementation]
- [Pattern or approach to follow/avoid]
- [Gotcha or edge case to remember]
### Still Open/Unclear
- [Questions that weren't resolved]
- [Decisions that were deferred]
### Relevance Assessment
[1-2 sentences on whether this information is still applicable and why]
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 · 159 lines · 56 tokens per session scan A e9637f9e4d16
artifact-analyzer is an agent published in the GitHub repository lucasnad27/claude-plugins (3 stars, last pushed 7d ago), licensed MIT. It adds 56 tokens to every session and 1,152 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to thoughts-analyzer, differing in 30 lines, and is treated as a copy.
Other agents, from other repositories
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
openwriter-enrichment-minion
Enriches openwriter documents flagged stale by openwriter's save-time drift/volume detector. Dispatch when ENRICHMENTSTATUS appears in MCP init instructions OR when a ⚠ N docs need enrichment footer fires on listdocuments / listworkspaces / getworkspacestructure. Reads each dirty doc and stamps it with a single field…
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
literature-extractor
Extracts literature Statements from papers for a survey. Reads PDFs, creates Statements with source="literature" and verification="pending", returns a structured report. Never registers theme tags, never creates Warrants or Claims.
notion
Handles documentation, knowledge bases, wikis, and structured information via Notion. Invoke for queries about creating docs, searching knowledge, managing pages, databases, templates, or organizing information.
ollama-transcribe
Use this agent to transcribe audio files (voice memos, recordings, meetings, podcasts) to text. Uses local mlx-whisper. Use whenever the user wants audio converted to text or references an .mp3, .wav, .m4a, .webm file.