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/implement_specsnpx skills add qinghaoliqaq/AutoCoder --skill implement_specsgit 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.00059 | $0.01129 |
| Opus 5 | $0.00030 | $0.00564 |
| Sonnet 5 | $0.00012 | $0.00226 |
| Haiku 4.5 | $0.00006 | $0.00113 |
Grade A, and why
implement-specs 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 3d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Specs
This skill turns a specs/<id>/TECH.md into committed code. Its core
discipline:
The spec and the code update in the same PR. A drifted spec is worse than no spec — it lies. Treat drift as a bug, not a normal outcome.
When To Use
Use this skill when:
- A
specs/<id>/TECH.mdalready exists and is approved (either by the user or by a previouswrite-tech-specrun) - The user says "implement spec X" or "follow the plan in specs/Y/"
- You're picking up an in-progress spec implementation (PROJECT_LOG.md exists)
Do not start implementing without a spec — drop back to
write-tech-spec first, or implement directly if the work is too small
to spec.
Operating Loop
For each numbered step in the spec's Implementation Plan:
- Re-read the spec. It may have been updated since you last looked.
- Read the cited current-state code. TECH.md cites
file:lineanchors; verify they still point where the spec claims. If the code has moved, update the spec citations first, then continue. - Implement the step. Stay scoped to what this step describes — don't drag in unrelated cleanup, refactors, or "while I'm here" improvements. Those belong in their own PRs.
- Run the testing scenarios the spec lists for this step. If the spec doesn't list one, add the smallest test that exercises the new behavior end-to-end.
- Update the spec if reality diverged. Common cases:
- You discovered the proposed approach doesn't work → update Proposed Changes and Implementation Plan, then re-read step 1.
- You found a missed dependency / risk → log it in
DECISIONS.md(create if absent) with a one-line rationale. - You finished early and a planned step is no longer needed → strike it from the plan with a note explaining why.
- Commit. Spec edits and code edits go in the same commit. Commit
messages reference the spec id:
feat(<id>): <step summary>.
PROJECT_LOG.md Discipline
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.
- 3d ago First seen · 127 lines · 59 tokens per session scan A a474f584b74e
implement-specs is a skill published in the GitHub repository qinghaoliqaq/AutoCoder (11 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,129 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
github-pr-workflow
Full pull request lifecycle — create branches, commit changes, open PRs, monitor CI status, auto-fix failures, and merge. Works with gh CLI or falls back to git + GitHub REST API via curl.
squash-merge
Squash-merge a PR into zeroclaw-labs/zeroclaw master with fully preserved commit history in the squash message body. Use this skill when the user explicitly mentions squash-merging, merging a specific PR number, landing a PR, or 合入 — e.g. "squash-merge #123", "merge PR 456", "land #789", "合入 #123", "/squash-merge…
submit-pr-from-current-changes
Create a branch, commit existing local changes, push them, and open a pull request. Use when submitting current work as a PR.
dispatch
Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it"…
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-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 失败'…