What is cliare-artifact-review?

A guide for reviewing one CLIARE measurement-artifact directory, a folder of files that records how a command-line tool was measured. It explains how to connect scores, issues, reports, commands, and runtime evidence without claiming more than the files show.

Use it to investigate a CLIARE run, explain its score, triage issues, find supporting evidence, or propose command-line remediation work.

It turns scattered measurement files into evidence-based explanations of score changes and problems. This helps reviewers decide what should be fixed next.

cliare-artifact-review — Skill for Claude Code and Codex by modiqo: A guide for reviewing one CLIARE measurement-artifact directory, a…

Install

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.

agentmods

npx agentmods add skills/modiqo/cliare/cliare-artifact-review

Any agent

npx skills add modiqo/cliare --skill cliare-artifact-review

Clone the repo

git clone --depth 1 https://github.com/modiqo/cliare

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/modiqo/cliare/cliare-artifact-review.svg)](https://agentmods.dev/skills/modiqo/cliare/cliare-artifact-review)

Your own site

<a href="https://agentmods.dev/skills/modiqo/cliare/cliare-artifact-review"><img src="https://agentmods.dev/badge/skills/modiqo/cliare/cliare-artifact-review.svg" alt="Measured on agentmods" height="20"></a>

Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,234 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00062	$0.02234
Opus 5	$0.00031	$0.01117
Sonnet 5	$0.00012	$0.00447
Haiku 4.5	$0.00006	$0.00223

Measured 5d ago against content hash 78e28d9c04b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cliare-artifact-review 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 5d 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.

skills/cliare-artifact-review/SKILL.md · 193 lines

How it starts

The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLIARE Artifact Review

What This Is

This skill is for reviewing one CLIARE measurement directory. It helps an agent connect the artifact map, scorecard, reviewable issues, persona reports, command index, condition dictionary, raw command shape, and runtime evidence without overstating the data.

Use it when a maintainer, harness author, platform engineer, security reviewer, researcher, or release owner asks what a CLIARE run means and what should be fixed next.

Work from the artifact directory. Prefer evidence-backed explanations over raw JSON excerpts.

Command Discipline

Prefer direct file reads and jq over ad hoc scripts. Do not use Python, cd, shell redirection, heredocs, or compound shell commands for routine artifact inspection. Keep shell commands simple and pass the artifact path directly to each file argument.

Good:

jq '{score:.summary.score,top_issues:[.top_issues[] | {id,severity,category,confidence,title}]}' /tmp/cliare-run/persona-harness.json

Avoid changing directories, shell redirection, and ad hoc scripts for basic artifact inspection.

Workflow

Identify the persona. If the user does not specify one, default to maintainer for CLI implementation work, harness for agent routing, security for approval/policy, and platform for CI gates.
Orient to the folder before reading raw artifacts. If artifact-map.json is missing, generate it:

cliare describe <artifact-dir> --write

Then read the map:

jq '{kind:.artifact_kind,health:.health,navigation:.navigation,missing_required:.missing_required,summaries:.summaries}' <artifact-dir>/artifact-map.json

Read posture:

jq '{score:.score.total,status:.score.status,model:.score.model,coverage:{commands_discovered:.coverage.commands_discovered,commands_runtime_confirmed:.coverage.commands_runtime_confirmed,traversal_complete:.coverage.traversal_complete,budget_exhausted:.coverage.budget_exhausted,observed_max_depth:.coverage.observed_max_depth,max_depth:.coverage.max_depth,probes_completed:.coverage.probes_completed,max_probes:.coverage.max_probes}}' <artifact-dir>/scorecard.json

Read the full file on GitHub · 193 lines

Changes

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.

5d ago First seen · 193 lines · 62 tokens per session scan A 78e28d9c04b0

Subscribe to this mod's changes

cliare-artifact-review is a skill published in the GitHub repository modiqo/cliare (487 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 62 tokens to every session and 2,234 once invoked, about $0.0003 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.

Debugging ai ai-agents cli

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens