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 agentmods add skills/sequenzia/agent-alchemy/verifynpx skills add sequenzia/agent-alchemy --skill verifygit clone --depth 1 https://github.com/sequenzia/agent-alchemyWhat 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.00063 | $0.01115 |
| Opus 5 | $0.00032 | $0.00558 |
| Sonnet 5 | $0.00013 | $0.00223 |
| Haiku 4.5 | $0.00006 | $0.00112 |
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 2d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solution Verifier
Verify competitive programming and LeetCode solutions for correctness through static analysis, automated test case generation, and execution.
CRITICAL: Complete ALL 4 phases. Do not stop after static analysis.
Phase 1: Parse Input
Goal: Extract the problem statement and solution code.
Parse $ARGUMENTS to extract:
- Problem statement — the full problem description with constraints, I/O format, and examples
- Solution code — the user's Python solution (inline code, file path, or pasted)
If both are in $ARGUMENTS, separate them. The problem statement typically comes first, followed by the solution code in a code block or after a separator.
If the solution is a file path, read it:
Read [file_path]
If the problem statement is missing, ask for it:
AskUserQuestion:
question: "Please provide the problem statement for verification. I need it to generate test cases and validate correctness."
options:
- label: "Paste problem text"
description: "Paste the full problem statement with constraints and examples"
- label: "Describe the problem"
description: "Describe what the problem asks — I'll generate test cases from that"
If the solution code is missing, ask for it:
AskUserQuestion:
question: "Please provide your solution code to verify."
options:
- label: "Paste code"
description: "Paste your Python solution code"
- label: "Provide file path"
description: "Give the path to your solution file"
If the solution is not Python, note this to the user and proceed with analysis (the verifier agent will handle language adaptation).
Phase 2: Spawn Verifier Agent
Goal: Delegate verification to the specialized agent.
Use the Task tool to spawn the solution-verifier agent:
Task:
subagent_type: "agent-alchemy-cs-tools:solution-verifier"
prompt: |
## Problem Statement
[full problem text with all constraints, I/O format, and examples]
## Solution Code
```python
[the user's solution code]
```
Perform full verification following your structured process:
1. Static analysis for logic errors and edge case handling
2. Generate test cases (basic, edge, stress)
3. Write and execute test harness
4. Compile report with verdict
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.
- 2d ago First seen · 137 lines · 63 tokens per session scan A 9219cb193a7f
verify is a skill published in the GitHub repository sequenzia/agent-alchemy (43 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 1,115 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.
Other skills, from other repositories
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
agent-workspace-linux
Use when a task needs an isolated hidden Linux desktop or workspace-owned browser: GUI app QA, web/browser/shopping automation, sandboxed app observation, or stale workspace cleanup. Routes agent-workspace-linux MCP tools on demand. Does NOT apply to host desktop/Chrome control, generic MCP setup, or pure code/file…
ss-component
Generate a new UI component following the StyleSeed design conventions.
loongsuite-pilot-insight
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用；包含 AI Coding 事件表语义，以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE，通常与 sls-dashboard-builder 一起使用。.
map-review
Interactive 4-section code review using monitor, predictor, and evaluator agents plus the user and maintainer role reviewers on current changes. Use when reviewing a diff, PR, or staged work before merge. Do NOT use to plan or implement; use map-plan or map-efficient.
map-fast
Minimal workflow for small, low-risk changes — no planning, no learning.