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.
git clone --depth 1 https://github.com/engindemirog/ai-native-engineering-workspaceWrote 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/commands/engindemirog/ai-native-engineering-workspace/verify)<a href="https://agentmods.dev/commands/engindemirog/ai-native-engineering-workspace/verify"><img src="https://agentmods.dev/badge/commands/engindemirog/ai-native-engineering-workspace/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/commands/engindemirog/ai-native-engineering-workspace/verify"><img src="https://agentmods.dev/badge/commands/engindemirog/ai-native-engineering-workspace/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.00017 | $0.00145 |
| Opus 5.5 | $0.00007 | $0.00058 |
| Sonnet 5.5 | $0.00003 | $0.00029 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
verify 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 22d 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.
What it actually says
Read AGENTS.md, docs/roles/qa.md, and workflows/segments.md. Run the VERIFY segment for spec $ARGUMENTS. Soft entry check: triage is complete — if no review/triage record exists, say so and ask.
Use prompts/verify.md: run tests to capture real output and produce the criterion ↔ evidence table; a claim without evidence is a gap, and gaps are findings. Do not write or modify any production code. Write the handoff, STOP. Do not ship, merge, or move files.
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.
- 22d ago Changed · +4 lines · +7 tokens per session 9509b0ca1868
- 1mo ago First seen · 8 lines · 10 tokens per session scan A 1ce817df7478
verify is a command published in the GitHub repository engindemirog/ai-native-engineering-workspace (87 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 145 once invoked, about $0.0001 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 commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.