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/wasintoh/toh-framework/engineer-harnessnpx skills add wasintoh/toh-framework --skill engineer-harnessgit clone --depth 1 https://github.com/wasintoh/toh-frameworkWrote 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/wasintoh/toh-framework/engineer-harness)<a href="https://agentmods.dev/skills/wasintoh/toh-framework/engineer-harness"><img src="https://agentmods.dev/badge/skills/wasintoh/toh-framework/engineer-harness.svg" alt="Measured on agentmods" 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 | $0.00109 | $0.02736 |
| Opus 5 | $0.00055 | $0.01368 |
| Sonnet 5 | $0.00022 | $0.00547 |
| Haiku 4.5 | $0.00011 | $0.00274 |
Grade A, and why
engineer-harness 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 4d 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🛠️ Engineer Harness Skill
Purpose: Shared harness for the main commands — pick tools like a senior engineer, talk like a human, suggest what's next Version: 1.1.0 For: Toh Framework v2.0.0+ Used by:
/toh,/toh-plan,/toh-fix,/toh-vibe(main commands) — MANDATORY · pairs withorchestration-protocolReplaces: the two legacy reporting skills (human report + next-step suggestions), now merged
🎯 Purpose
Three things every engineer-grade delivery needs, in one skill:
- Tool Selection Rules — reach for the right tool instead of guessing from memory
- Non-dev Communication Mode — report results a non-technical user actually understands
- Stage-Aware Next Actions + Announce Contract — never leave the user wondering "what now?"
Golden Rule: "If the user has to ask a follow-up question, the response wasn't complete enough."
🧰 A. Tool Selection Rules
Act like a senior engineer choosing tools — never fake it from memory.
| Situation | ❌ Don't | ✅ Do |
|---|---|---|
| Unsure about an API / version | Write from memory | Search real docs first (Context7 / web) before writing a line |
| Fixing a bug | Diagnose by reading only | Reproduce / run it first, then diagnose from evidence |
| Several independent tasks | Do them one by one | Delegate in parallel (sub-agents / parallel tool calls) |
| Before delivering | "น่าจะได้แล้ว" / "should work" | Build and actually look at the result (open it, run it) |
| Unfamiliar library | Assume the API shape | Read the real node_modules types / README |
Rule of thumb: evidence over assumption, always. If a fact is checkable, check it before you write.
THE EVIDENCE RULE (verification): Run the check. Quote the failing lines. Fix what the quote shows. Re-run. Only a quoted passing run counts as done. A sub-agent's "done" report is evidence to verify, never proof.
💬 B. Non-dev Communication Mode
The user is usually not a developer. Report like an engineering team that customers love.
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.
- 4d ago First seen · 234 lines · 109 tokens per session scan A e483c51aa7d4
engineer-harness is a skill published in the GitHub repository wasintoh/toh-framework (95 stars, last pushed yesterday), licensed MIT. It adds 109 tokens to every session and 2,736 once invoked, about $0.0005 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
smoke-test
End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke…
image-generation
Use this skill when the user requests to generate, create, imagine, or visualize images including characters, scenes, products, or any visual content. Supports structured prompts and reference images for guided generation.
podcast-generation
Use this skill when the user requests to generate, create, or produce podcasts from text content. Converts written content into a two-host conversational podcast audio format with natural dialogue.
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
skill-reviewer
Reviews DeerFlow skill packages for readiness, triggers, safety boundaries, resources, and evidence. Invoke when users ask to audit, grade, or production-check an existing skill.
surprise-me
Create a delightful, unexpected "wow" experience for the user by dynamically discovering and creatively combining other enabled skills. Triggers when the user says "surprise me" or any request expressing a desire for an unexpected creative showcase. Also triggers when the user is bored, wants inspiration, or asks for…