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 skills add chan4lk/specclaw --skill author-specgit clone --depth 1 https://github.com/chan4lk/specclawWrote 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/chan4lk/specclaw/author-spec)<a href="https://agentmods.dev/skills/chan4lk/specclaw/author-spec"><img src="https://agentmods.dev/badge/skills/chan4lk/specclaw/author-spec/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/skills/chan4lk/specclaw/author-spec"><img src="https://agentmods.dev/badge/skills/chan4lk/specclaw/author-spec.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.00104 | $0.00501 |
| Opus 5 | $0.00052 | $0.00251 |
| Sonnet 5 | $0.00021 | $0.00100 |
| Haiku 4.5 | $0.00010 | $0.00050 |
Grade A, and why
author-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 9d 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
specclaw author-spec
First, run specclaw-ensure-init .specclaw — idempotently creates .specclaw/ if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name).
Interactively author spec.md for an approved proposal.
- Validate: run
specclaw-validate-change .specclaw <change> plan. If it fails (typically:proposal.mdmissing), report the missing prerequisite and stop. - Check for existing spec: if
.specclaw/changes/<change>/spec.mdalready exists, show the user the first few lines and ask whether to overwrite. Default is no — abort if the user does not explicitly confirm overwrite. - Invoke the agent: call the
spec-authorsubagent via theAgenttool withsubagent_type: "spec-author"and a prompt instructing it to author the spec for<change>. The agent readsproposal.mdand writesspec.mditself; do not wrap the dialogue in this skill. - Update status:
specclaw-update-status .specclaw. - GitHub sync (if
github.sync: trueinconfig.yaml):specclaw-gh-sync update .specclaw <change>to refresh the issue with the new spec. - Azure Boards sync (if
azdo.boards.sync: true):specclaw-azdo-issue update .specclaw <change>.
Do not proceed to /specclaw:plan automatically. After spec.md is written, the user can run /specclaw:plan <change> (which will use the freshly-authored spec.md and generate design.md + tasks.md) when ready.
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.
- 9d ago First seen · 19 lines · 104 tokens per session scan A b4ecd8be5aad
author-spec is a skill published in the GitHub repository chan4lk/specclaw (12 stars, last pushed 5d ago), licensed MIT. It adds 104 tokens to every session and 501 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
upload-assets
An asset-upload workflow that sends files to a console’s content-delivery network and prepares a review-request payload for a person to submit.
review-spec
A workflow for comparing an existing feature specification with the project's review checklist and implementation. It looks for missing requirements, differences between documented screens and actual screens, and lessons from rejected submissions.
wire-sdk
An SDK integration guide for 앱인토스, a platform for building apps inside Toss. It covers permissions, persistent storage, sharing links, screen controls, safe-area spacing, and secure WebSocket connections.
optimize-seo-geo
A workflow for filling only the SEO and GEO sections of a post's front matter. SEO helps a page appear in search results, while GEO prepares information for answer systems that may quote or cite it.
write-spec
A feature-specification workflow that turns a feature request into a Markdown file describing screens, acceptance checks, boundaries, and unanswered questions.
delegating-work
Use when named delegation is a genuine option for current work, when preparing or reviewing a handoff, or when continuing delegated work to a verified outcome. It supplies context recovery, deliberate skill selection, necessary-only delegation, evidence requirements, and continuation discipline. Do not use for…