Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/keepYaoung/artifact-organizernpx agentmods add skills/keepyaoung/artifact-organizer/artifact-organizer-diffWrote 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/keepyaoung/artifact-organizer/artifact-organizer-diff)<a href="https://agentmods.dev/skills/keepyaoung/artifact-organizer/artifact-organizer-diff"><img src="https://agentmods.dev/badge/skills/keepyaoung/artifact-organizer/artifact-organizer-diff/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/skills/keepyaoung/artifact-organizer/artifact-organizer-diff"><img src="https://agentmods.dev/badge/skills/keepyaoung/artifact-organizer/artifact-organizer-diff.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.00080 | $0.01474 |
| Opus 5 | $0.00040 | $0.00737 |
| Sonnet 5 | $0.00016 | $0.00295 |
| Haiku 4.5 | $0.00008 | $0.00147 |
Grade A, and why
artifact-organizer-diff 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 9d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 0 — Preference: Before running any renderer command, perform the theme-preference resolution block from the base
artifact-organizerskill (~/.claude/skills/artifact-organizer/SKILL.md, section "Step 0"). It sets$THEMEand$RENDERER. If absent, this wrapper falls back tonotion+auto.
Artifact Organizer — Diff review mode
Produces a self-contained HTML diff review using artifact-organizer/CodeDiff, artifact-organizer/ArchitectureGrid (for impacted modules), and artifact-organizer/Callout (for risks). Thin wrapper over the artifact-organizer skill.
When to use
- User pastes a unified diff or
git diffoutput and asks for review/summary. - User gives a PR URL (
github.com/owner/repo/pull/N) and asks for review. - User gives a git range (
main..HEAD,HEAD~5..HEAD, SHA range). - User says "review these changes", "what changed", "impact of this diff".
Do not use for: generic commit history summaries (no concrete diff), feature spec writing, or rendering a single code snippet (use hyperscribe with CodeBlock).
Source detection
- Git range — run
git diff <range>to get the unified diff. - PR URL — use
gh pr diff <N> -R owner/repoorgh api repos/owner/repo/pulls/<N>.diff. - Pasted diff — use the provided text directly.
- No clear source — ask the user before continuing.
Envelope structure
{
"a2ui_version": "0.9",
"catalog": "artifact-organizer/v1",
"is_task_complete": true,
"parts": [
{
"component": "artifact-organizer/Page",
"props": { "title": "Diff: <short summary>", "subtitle": "<N files, +X -Y lines>", "toc": true },
"children": [
{
"component": "artifact-organizer/Section",
"props": { "id": "summary", "title": "Summary", "lead": "**What changed** and **why it matters**." },
"children": [
{ "component": "artifact-organizer/Prose", "props": { "markdown": "One-paragraph summary." } },
{ "component": "artifact-organizer/ArchitectureGrid", "props": {
"layout": "grid",
"nodes": [ { "id": "auth", "title": "Auth module", "tag": "modified" } ]
}}
]
},
{
"component": "artifact-organizer/Section",
"props": { "id": "risks", "title": "Risks" },
"children": [
{ "component": "artifact-organizer/Callout", "props": { "severity": "warn", "title": "Migration required", "body": "..." }}
]
},
{
"component": "artifact-organizer/Section",
"props": { "id": "changes", "title": "Changes" },
"children": [
{ "component": "artifact-organizer/CodeDiff", "props": {
"filename": "src/auth.ts",
"lang": "ts",
"hunks": [ { "before": "const x = 1;", "after": "const x = 2;", "atLine": 42 } ]
}}
]
}
]
}
]
}
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.
- 9d ago First seen · 130 lines · 80 tokens per session scan A 65f6bd4e6781
artifact-organizer-diff is a skill published in the GitHub repository keepYaoung/artifact-organizer (2 stars, last pushed 2mo ago), licensed MIT. It adds 80 tokens to every session and 1,474 once invoked, about $0.0004 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
security-review
Review code for security vulnerabilities. Use when the user says 'security review', 'security audit', 'check for vulnerabilities', 'pentest the code', 'OWASP check', or any variation of wanting a security assessment.
verifying-claims
Check that a document's claims about code are actually true by reading the prose, the code, and the tests and reporting (or fixing) where they disagree. Use whenever the user wants to verify a README, guide, spec, or docstring still matches the code; whenever they mention documentation drift, doc-code sync, "is this…
reasoning-semiformally
Apply semi-formal certificate reasoning to code analysis — patch verification, fault localization, patch equivalence. Use when reviewing patches, hunting bugs across scopes, comparing fixes, or when code reasoning requires tracing execution across files/modules. Triggers on code review, bug localization, patch…
mdma-integration
Integrate MDMA into an application and build features with it — wire up parsing, the runtime store, React rendering, LLM streaming, custom components, prompts, and CI validation. Use this skill when the user asks to add MDMA to an app, build a chat that streams MDMA, author or maintain a custom prompt, validate MDMA…
claude-md-drift-audit
Audit every CLAUDE.md in this project for drift against the last week of git history. Flags sections that reference deleted files, renamed paths, or removed dependencies. Read-only — returns a punch list, never edits.
alibaba-iac-change-safety-review
Review Terraform and ROS (Resource Orchestration Service) changes targeting Alibaba Cloud — blast radius analysis, resource deletion detection, cross-stack dependency impact, Resource Directory scope, and rollback plan completeness.