Borrowing it
Nothing to install: this file belongs to ambient-code/agentready. 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/ambient-code/agentready/main/.claude/skills/test-assess/SKILL.mdgit clone --depth 1 https://github.com/ambient-code/agentreadyWrote 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/ambient-code/agentready/test-assess)<a href="https://agentmods.dev/skills/ambient-code/agentready/test-assess"><img src="https://agentmods.dev/badge/skills/ambient-code/agentready/test-assess/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/ambient-code/agentready/test-assess"><img src="https://agentmods.dev/badge/skills/ambient-code/agentready/test-assess.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Excessive Agency · line 76 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00075 | $0.00770 |
| Opus 5.5 | $0.00030 | $0.00308 |
| Sonnet 5.5 | $0.00015 | $0.00154 |
| Haiku 4.5 | $0.00007 | $0.00077 |
Grade A, and why
test-assess 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 2mo 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test agentready assess on real repositories
You are testing the agentready assessment tool against real GitHub repositories to validate that a change works correctly.
1. Determine what to test
The user will describe what assessor behavior they want to validate (e.g., "test Husky detection", "verify the new CI gates assessor"). If the description is unclear, ask a brief clarifying question.
2. Ensure the code under test is checked out
Check which branch is currently active. If the change being tested is on a
different branch or PR, check it out first. If it is a PR, use
gh pr checkout <number>.
3. Select repositories
Search GitHub for repositories that are relevant to the feature being tested. For example, if testing Husky hook detection, find repos that use Husky.
How many repos:
- Small or targeted changes: at least 1 repo
- Larger or riskier changes: 3 to 5 repos
Selection criteria (in priority order):
- Relevance: repos must exercise the specific behavior being tested. This is the most important criterion.
- Variety of maturity: when possible, mix large popular projects with smaller or newer ones. But never sacrifice relevance for variety.
Use gh search repos, gh api, or gh search code to find candidates.
Briefly confirm your repo selections with the user before cloning.
4. Clone repos to a temp directory
Create a unique temp directory for this test run:
TESTDIR=$(mktemp -d /tmp/agentready-test-XXXXXX)
Shallow clone each repo into that directory:
git clone --depth 1 <repo-url> $TESTDIR/<repo-name>
5. Run assessments
Run each assessment using the local checkout, not the globally installed package:
yes | PYTHONPATH=src python -m agentready assess $TESTDIR/<repo-name>
The yes | prefix auto-confirms the large-repo prompt if it appears.
6. Report results
After each assessment completes, report to the user:
- The repo name and the overall score/certification level
- The specific finding(s) relevant to what is being tested, including status, score, and evidence
- The exact paths to the JSON, HTML, and Markdown reports so the user can inspect them
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.
- 2mo ago First seen · 99 lines · 75 tokens per session scan A a61600b8e53d
test-assess is a skill published in the GitHub repository ambient-code/agentready (154 stars, last pushed 3d ago), licensed MIT. It adds 75 tokens to every session and 770 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-30.
Other skills, from other repositories
qa
QA-test a website or web app and return a 1-5 quality score (5 = flawless, 1 = broken) with evidence. Use when the user wants to test, QA, evaluate, score, or "check how good" a site, page, flow, or app — including a local dev server (e.g. "qa test localhost:5173", "does the checkout work?", "rate this landing page").…
test-writer
Generate comprehensive test suites for existing code.
openspec-plus-tdd
MANDATORY skill that activates whenever code is written to implement an OpenSpec change task. Triggers: openspec-plus-apply is active, /opsx-apply is running, the user is implementing tasks from an OpenSpec change, an implementer subagent dispatched by openspec-plus-apply is starting work, or the user invokes phrases…
test-writer
Write tests with TDD following structured patterns. Ensures consistent AAA structure, proper coverage targets, and framework-specific conventions. Without this skill, tests lack consistent naming, miss coverage targets, and skip anti-pattern checks.
bugfix-quick
Fast bug fixes with root cause investigation + TDD. Enforces 'no fix without root cause' discipline and verification protocol. Without this skill, fixes are applied at symptoms instead of sources, and bugs return.
refactor-expert
Guide safe, incremental refactoring that improves code quality without changing behavior.