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 chekusu/wanman --skill artifact-qualitygit clone --depth 1 https://github.com/chekusu/wanmanWrote 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/chekusu/wanman/artifact-quality)<a href="https://agentmods.dev/skills/chekusu/wanman/artifact-quality"><img src="https://agentmods.dev/badge/skills/chekusu/wanman/artifact-quality.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.00018 | $0.00500 |
| Opus 5 | $0.00009 | $0.00250 |
| Sonnet 5 | $0.00004 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
artifact-quality 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 7d 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.
What it actually says
Artifact Quality Standards
Required Fields
Every artifact's metadata must include:
| Field | Type | Description |
|---|---|---|
source |
string | Data source identifier |
confidence |
number (0-1) | Confidence score |
Source Identifier Format
training_data → From model training data (lowest confidence)
estimate → Extrapolated from known data
web_search:<domain> → Web search result, specify the domain
government_data → Official government data
industry_report → Industry report
api:<service> → API call result
cross_validated → Cross-validated
Confidence Scoring Guide
0.9+ → Official data, multi-source validated
0.7-0.9 → Reliable source, single validation
0.5-0.7 → Web search result, not cross-validated
0.3-0.5 → Extrapolation/estimate with reasonable basis
0.1-0.3 → Training data or rough estimate
Cross-Validation
When the CEO or another agent validates an artifact, update the metadata:
wanman artifact put --kind market_data --path "competitors/pricing" \
--meta '{"source":"cross_validated","confidence":0.85,"verified":true,"verified_by":"ceo","verified_at":"2024-01-15","original_source":"web_search:dianping.com","validation_notes":"consistent with Meituan data"}'
Common Quality Issues
- Missing source:
sourceis empty or just says "internet" - Inflated confidence: Estimated data labeled 0.9+
- Missing units: Amounts without currency, areas without units
- Vague timing: No data collection date specified
- Inconsistent paths:
pathdoes not follow a consistent naming convention
Path Naming Convention
costs/{category}/{item} → Cost data
revenue/{scenario}/{period} → Revenue forecasts
competitors/{name}/{metric} → Competitor data
market/{segment}/{metric} → Market data
location/{area}/{metric} → Location data
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.
- 7d ago First seen · 65 lines · 18 tokens per session scan A aa0aca93274b
artifact-quality is a skill published in the GitHub repository chekusu/wanman (681 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 500 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-30.
Other skills, from other repositories
docx
Read, edit, or create Microsoft Word .docx files. Trigger this skill whenever the user mentions a Word document, .docx file, contract, report, brief, memo, or asks to extract text, modify an existing doc, generate one from a brief, or audit tracked changes. Three execution paths: text-and-structure extraction…
pdf-toolkit
Structured .pdf operations: extract text/tables, merge pages from multiple PDFs, split a PDF by page ranges, fill PDF form fields, and generate fresh PDFs from JSON. Trigger when the user wants programmatic PDF work without natural-language rewriting — examples: pull tables from a report, combine three PDFs, extract…
xlsx
Read, edit, or create Microsoft Excel .xlsx workbooks. Trigger this skill whenever the user mentions a spreadsheet, .xlsx file, workbook, sheet, formula, pivot table, or asks to extract tabular data, modify a sheet, or build a workbook from rows. Three execution paths: structured inspection, in-place cell edits, and…
nano-pdf
Edit PDFs with natural-language instructions using the nano-pdf CLI.
liteparse
Use this skill when the user asks to parse, perform multi-format document conversion or spatially extract text from an unstructured file (PDF, DOCX, PPTX, XLSX, images, etc.) locally without cloud dependencies.
meta-pdf-intelligence
Use this meta-skill instead of answering directly when the user needs PDF analysis, pasted PDF excerpt analysis, digesting, comparison, or question answering that benefits from multi-skill orchestration across PDF extraction, summarization, cross-document synthesis, traceable evidence indexing, and memory capture.