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 wanshuiyin/ARIS-Movie-Director --skill comic-blind-comparison-reviewgit clone --depth 1 https://github.com/wanshuiyin/ARIS-Movie-DirectorWrote 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/wanshuiyin/aris-movie-director/comic-blind-comparison-review)<a href="https://agentmods.dev/skills/wanshuiyin/aris-movie-director/comic-blind-comparison-review"><img src="https://agentmods.dev/badge/skills/wanshuiyin/aris-movie-director/comic-blind-comparison-review/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/wanshuiyin/aris-movie-director/comic-blind-comparison-review"><img src="https://agentmods.dev/badge/skills/wanshuiyin/aris-movie-director/comic-blind-comparison-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Privilege Escalation · line 19 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Privilege Escalation · line 50 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Privilege Escalation · line 497 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Privilege Escalation · line 29 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Privilege Escalation · line 121 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00000 | $0.11604 |
| Opus 5 | $0.00000 | $0.05802 |
| Sonnet 5 | $0.00000 | $0.02321 |
| Haiku 4.5 | $0.00000 | $0.01160 |
Grade B, and why
comic-blind-comparison-review scanned grade B with 1 finding 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 12d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
> A single coin-flip seals `.ab_mapping.json` and `chmod 600`s it **before any reviewer is invoked**; the How it starts
The opening of the file, as written. The whole thing — 544 lines — stays where its author put it; the contents beside it link to each section on GitHub.
comic-blind-comparison-review — Double-Blind A/B of Two Finished Comics (Phase 1, step S12, post-final)
The "vs baseline" capability the comic side otherwise lacks. The per-panel
comic-director panel_gate and the cross-panel assembly_gate operate
during production on single units; this skill operates after production, on two complete works —
our cross-model-audited progressive comic (authored by the comic-author suite,
baked by comic-director) vs a naive single-prompt one-shot baseline — and
proves the spiral pipeline beats the one-shot, under a blind so neither reviewer can favor the home team.
It is a direct, faithful port of aris_movie's blind-comparison-review from video to a whole-comic A/B
(outputs/aris_movie_progressive.mp4 vs outputs/baseline_sd2_naive.mp4 → two rendered comic page sets), and
it is an evaluation skill, not an authoring one: it never edits a comic, it judges two finished ones.
Cardinal lesson baked in as a gate, not prose: the order of operations IS the integrity guarantee. A single coin-flip seals
.ab_mapping.jsonandchmod 600s it before any reviewer is invoked; the seal's mtime MUST precede both reviews; from seal-time until UNSEAL the orchestrator (Claude) may not read or quote the mapping; any home-team token in a reviewer prompt is a HARD-ABORT, not a warning. If the orchestrator reads the mapping before both reviews land, it may subconsciously phrase the synthesis to favor the home team — so the timestamp ordering is the audit trail, and "blinding integrity" is REPORTED, never assumed.
progressive comic ┐ ┌─▶ comparison.md (Chinese deliverable)
(our audited) ├─▶ ⓪ SEAL .ab_mapping.json (1 coin-flip, │
baseline comic ┘ chmod 600, mtime BEFORE any reviewer) │
(naive one-shot) │ ▼ │
│ ① STAGE pages → A/ and B/ (sealed ids) │
│ ▼ │
│ ② CODEX blind review (xhigh, RO) ─────┤ (no home-team token; reads SHARED
│ ▼ │ blind spec = intent + ART_BIBLE only)
│ ③ GEMINI blind review (per-page + ─────┤
│ synthesis, auto-gemini-3) │
│ ▼ │
└─▶ ④ UNSEAL (verify seal_ts < BOTH reviews) ┘
▼
⑤ WRITE comparison.md + ⑥ WIKI A/B verdict nodes + edges
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.
- 12d ago First seen · 544 lines · 0 tokens per session scan B ce9462d203a3
comic-blind-comparison-review is a skill published in the GitHub repository wanshuiyin/ARIS-Movie-Director (61 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 11,604 tokens. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
verification-loop
A comprehensive verification system for Claude Code sessions. Use when verifying a Claude Code session's work before claiming it is complete.
cli-eval
Create and run evaluation suites, watch live benchmark progress, view scorecards, compare model performance, and integrate eval runs with CI workflows from the CLI.
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.