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 PyModel/pythinker-cli --skill write-tech-specgit clone --depth 1 https://github.com/PyModel/pythinker-cliWrote 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/pymodel/pythinker-cli/write-tech-spec)<a href="https://agentmods.dev/skills/pymodel/pythinker-cli/write-tech-spec"><img src="https://agentmods.dev/badge/skills/pymodel/pythinker-cli/write-tech-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/pymodel/pythinker-cli/write-tech-spec"><img src="https://agentmods.dev/badge/skills/pymodel/pythinker-cli/write-tech-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00017 | $0.00215 |
| Opus 5.5 | $0.00007 | $0.00086 |
| Sonnet 5.5 | $0.00003 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00021 |
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 1mo 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
Write Tech Spec
Use when the user asks for a technical spec, implementation plan, architecture note, or product-spec-to-engineering breakdown.
Workflow
- Read the product requirements or issue context.
- Scout the relevant code paths, APIs, tests, and constraints.
- Propose the smallest architecture that satisfies the requirements.
- Identify data model, API, UI, migration, compatibility, and security implications.
- Define implementation phases and verification gates.
Rules
- Ground the spec in existing code evidence; cite paths where possible.
- Prefer incremental, reversible changes.
- Do not over-design speculative extension points.
- Surface open questions and risky trade-offs explicitly.
Output
# Technical Spec: <title>
## Context
## Existing Code Evidence
## Proposed Design
## Implementation Plan
## Testing / Verification
## Migration / Compatibility
## Security / Privacy
## Risks
## Open Questions
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.
- 1mo ago First seen · 40 lines · 17 tokens per session scan A 372494bc53b7
write-tech-spec is a skill published in the GitHub repository PyModel/pythinker-cli (21 stars, last pushed 3d ago), licensed Apache-2.0. It adds 17 tokens to every session and 215 once invoked, about $0.0001 per session on Opus 5.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
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
design-review
Deep design review of Go codebase — naming, structure, consistency, interfaces, error handling. Scores each dimension and provides actionable fixes.
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
agents-md
Generate AGENTS.md files for Go, Rust, TypeScript, and Java projects. Use this skill whenever the user asks to create, scaffold, bootstrap, update, or review an AGENTS.md (or agent-instructions, CLAUDE.md, repo guide for agents) file in a codebase. Also trigger when the user says "add AGENTS.md", "make this repo…
crossreview
Run when the user invokes /crossreview (or /crossreview:setup to choose the reviewers) or asks for a cross-review, a quorum review or a second opinion from other agents or models: fan a code review (uncommitted work, a branch, a commit range, files, a plan or a document) out to several console code agents (Claude…
code-review-pi
Review code for quality, run linters, check test coverage, fix issues, and enforce gates. Save the final report to ./specs/issues/003-code-review-pi/PROMPT.md. Use before committing changes.