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 qinghaoliqaq/AutoCoder --skill verifygit clone --depth 1 https://github.com/qinghaoliqaq/AutoCoderWrote 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/qinghaoliqaq/autocoder/verify)<a href="https://agentmods.dev/skills/qinghaoliqaq/autocoder/verify"><img src="https://agentmods.dev/badge/skills/qinghaoliqaq/autocoder/verify/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/qinghaoliqaq/autocoder/verify"><img src="https://agentmods.dev/badge/skills/qinghaoliqaq/autocoder/verify.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.00042 | $0.00597 |
| Opus 5.5 | $0.00017 | $0.00239 |
| Sonnet 5.5 | $0.00008 | $0.00119 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
verify scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Use curl/fetch to test affected API endpoints How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify — End-to-End Verification of Code Changes
Verify that recent code changes actually work by running the application and testing the affected functionality.
Approach
Step 1: Identify What Changed
- Read recent git diff or changed files to understand the scope of changes
- Identify which features, endpoints, or UI components were modified
- Determine what needs to be tested
Step 2: Build & Compile
- Run the project's build command (cargo build, npm run build, etc.)
- Fix any compilation or type errors
- Ensure the build completes cleanly with no warnings related to changes
Step 3: Run Existing Tests
- Execute the project's test suite (cargo test, npm test, etc.)
- If specific test files exist for changed modules, run those first
- Report any test failures — do NOT skip or ignore them
Step 4: Manual Verification
For backend changes:
- Start the server if applicable
- Use curl/fetch to test affected API endpoints
- Verify request/response shapes match expectations
- Test error cases (invalid input, auth failures, not found)
For frontend changes:
- Check that the dev server starts without errors
- Verify the changed UI renders correctly
- Test interactive elements (forms, buttons, navigation)
- Check responsive behavior if layout was changed
For library/utility changes:
- Write a small test script exercising the changed functions
- Verify edge cases mentioned in the change description
Step 5: Report
Provide a clear verification report:
VERIFICATION REPORT
==================
Build: PASS/FAIL (details if fail)
Tests: PASS/FAIL (X passed, Y failed — list failures)
Manual: PASS/FAIL (what was tested and results)
Overall: PASS/FAIL
If any step fails:
- Diagnose the root cause
- Fix the issue if it's clearly related to the recent changes
- Re-run verification after the fix
- Report what was fixed
Important Rules
- Do NOT claim "all tests pass" without actually running them
- Do NOT skip verification steps — if you can't run something, say so explicitly
- Do NOT fix unrelated issues during verification — only fix what the changes broke
- Report outcomes faithfully — failures are valuable information
- If the project has no test infrastructure, note this and focus on build + manual testing
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 · 85 lines · 42 tokens per session scan A abfe5959ca03
verify is a skill published in the GitHub repository qinghaoliqaq/AutoCoder (12 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 597 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
textual-ui-developer
Develop and debug the MassGen Textual TUI with deterministic replay, snapshot regression tests, and targeted runtime checks.
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
langbot-testing
Test LangBot WebUI and core product flows with an automated browser and backend logs. Use when validating the configured LangBot frontend, pipeline Debug Chat, model provider setup and test buttons, bot and knowledge-base UI flows, or troubleshooting failed LangBot end-to-end tests.
app_verification
Verify a newly created or newly installed Rome app after coding:appcreation or coding:workflowcreation finishes installing it. Use only as a second-pass verifier: receive the app id, source root, expected behavior, and local dashboard/API base URL from the creator, then visit the installed app, exercise its safe…
zafiro-qa
An Android quality-assurance workflow for testing the Zafiro app on a real phone or emulator. It uses one installed app as the test controller and a separate debug app as the app under test, with screenshots, device actions, settings, and logs.
voyager
Authoring web and native E2E tests, including Playwright, Appium, XCUITest, device farms, visual regression, and App Store screenshot pipelines. Not for unit/load tests.