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/qinghaoliqaq/autocoder/write_tech_specnpx skills add qinghaoliqaq/AutoCoder --skill write_tech_specgit clone --depth 1 https://github.com/qinghaoliqaq/AutoCoderWhat 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.00061 | $0.01148 |
| Opus 5 | $0.00030 | $0.00574 |
| Sonnet 5 | $0.00012 | $0.00230 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
write-tech-spec 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Tech Spec
This skill produces a technical specification grounded in the current
codebase, not a wish-list. The output is a markdown file at
specs/<id>/TECH.md that the team (or your future self) can review,
critique, and then hand back to an agent for implementation.
When To Use
Use this skill when:
- The user explicitly asks for a spec / tech spec / design doc
- The task touches more than two modules and requires a plan before diving in
- A naive implementation would risk breaking other parts of the codebase
- You're about to make a non-trivial architectural decision and want it written down before you commit
Do not use this for trivial fixes (one-line changes, typos, single- function refactors). Spec-writing has a fixed cost; spend it where it actually saves rework.
Spec Directory Layout
specs/<id>/
TECH.md ← this skill writes this
PRODUCT.md ← optional; product-level "what & why"
PROJECT_LOG.md ← optional; running log for multi-day work
DECISIONS.md ← optional; ADR-style decision records
<id> is one of:
- a GitHub issue id like
gh-1063 - a ticket id like
APP-3076 - a short kebab-case slug like
parallel-subtask-merge
Pick one and use it consistently. If unsure, ask the user (via
AskUserQuestion) or default to a slug derived from the task title.
TECH.md Required Sections
Every TECH.md must have these sections, in this order, with these exact H2 headings:
# <Title>
## Context
## Current State
## Proposed Changes
## End-to-End Flow
## Implementation Plan
## Testing
## Risks & Open Questions
Section guidance
-
Context (3–6 bullets) — Why are we doing this? What's the user- facing motivation? Link to the relevant PRODUCT.md or issue if one exists.
-
Current State — Summarize how the codebase handles the relevant area today. Every claim must be cited with a
file:linereference. Use Read / Grep to verify before citing. If you cite a file you didn't read, you've failed this skill.
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 · 140 lines · 61 tokens per session scan A bbbebd5aea07
write-tech-spec is a skill published in the GitHub repository qinghaoliqaq/AutoCoder (11 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 1,148 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
ha-skill-creator
Create, edit, improve, or audit Hope Agent skills. Use when the user wants to: (1) create a new skill from scratch, (2) edit or improve an existing skill, (3) review or clean up a SKILL.md file, (4) run evaluations to test skill effectiveness, (5) optimize skill descriptions for better trigger accuracy. Trigger…
ha-browser
Hope Agent browser automation — the standard status → tabs → snapshot → act loop, stale-ref recovery rules, and what to do when login / 2FA / captcha / camera-prompt / dialog blocks progress. Load this skill whenever you reach for the browser tool. Trigger on: user asks the agent to open / control / click / scrape /…
ha-logs
Self-service diagnostics — query Hope Agent's local SQLite databases (logs / sessions / background jobs) directly via the exec tool to investigate problems, analyze usage, and locate root causes. Trigger on: user reports something broken / failing / slow / stuck / not responding ('X 不工作', 'X 报错', 'X 卡住', '为什么 X 失败'…
ha-pet-import
Safely import, select, switch, or enable a compatible desktop pet in Hope Agent. Resolve packages from any origin, including local folders, zip archives, pet.json plus a sprite, PNG/WebP atlases, chat attachments, repository or cloud files, direct HTTPS artifact URLs, and download pages. Use whenever a user asks to…
email-draft
Use when the user asks to draft, polish, translate, or reply to an email. Produces a clean draft with subject line, greeting, body, and sign-off, plus a pre-send self-check.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…