Borrowing it
Nothing to install: this file belongs to AINative-Studio/oss-repo-check. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AINative-Studio/oss-repo-check/main/.claude/skills/quaid-scan/SKILL.mdgit clone --depth 1 https://github.com/AINative-Studio/oss-repo-checkWrote 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/ainative-studio/oss-repo-check/quaid-scan)<a href="https://agentmods.dev/skills/ainative-studio/oss-repo-check/quaid-scan"><img src="https://agentmods.dev/badge/skills/ainative-studio/oss-repo-check/quaid-scan/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/ainative-studio/oss-repo-check/quaid-scan"><img src="https://agentmods.dev/badge/skills/ainative-studio/oss-repo-check/quaid-scan.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.00084 | $0.01110 |
| Opus 5.5 | $0.00034 | $0.00444 |
| Sonnet 5.5 | $0.00017 | $0.00222 |
| Haiku 4.5 | $0.00008 | $0.00111 |
Grade A, and why
quaid-scan 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 1mo 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
quaid-scan Skill
Runs quaid-scanner against a local path or GitHub URL and interprets the results.
6 Pillars (weighted)
| Pillar | Weight | What it measures |
|---|---|---|
| Security | 25% | Supply chain, branch protection, token permissions, OpenSSF Scorecard |
| Governance | 20% | License, bus factor, vendor neutrality, asset protection |
| Community | 15% | Contributor funnel, response time, burnout signals, funding |
| AI Readiness | 15% | Model cards, agentic rules, dataset provenance |
| Inclusive | 15% | INI terms, diminishing language, assumed knowledge |
| Technical | 10% | Linting, test coverage, SemVer/CHANGELOG consistency |
CLI Reference
# Quick scan of current directory
node dist/cli.js . --depth quick
# Standard scan with JSON output
node dist/cli.js . --format json
# Thorough scan of a GitHub repo
node dist/cli.js https://github.com/owner/repo --depth thorough
# Markdown report to file
node dist/cli.js . --format markdown --output report.md
# With ecosystem intelligence (rivals, partners, community recommendations)
node dist/cli.js . --ecosystem
# With threshold (exit 2 if score < 6.0)
node dist/cli.js . --threshold 6.0
# Depth levels
# --depth quick ~5s — file presence checks, no API calls
# --depth standard ~15s — default, adds GitHub API checks
# --depth thorough ~60s — all checks including OpenSSF Scorecard API
Exit Codes
| Code | Meaning |
|---|---|
| 0 | Score ≥ 8.0 (Low Risk) |
| 1 | Score 5.0–7.9 (Medium Risk) |
| 2 | Score < 5.0 (High/Critical Risk) or --threshold not met |
How to Interpret Results
After running, interpret the JSON output:
overallScore: 3.3 → CRITICAL — immediate action needed on high-severity findings
riskLevel: CRITICAL
Priority order:
1. findings where severity = CRITICAL → block PR / release
2. findings where severity = WARNING → schedule for sprint
3. recommendations[0..2] → top actions by impact/effort ratio
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.
- 1mo ago First seen · 129 lines · 84 tokens per session scan A a3f0484b7c2e
quaid-scan is a skill published in the GitHub repository AINative-Studio/oss-repo-check (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 84 tokens to every session and 1,110 once invoked, about $0.0003 per session on Opus 5.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
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…