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/amatofrancesco99/thoughtweave/changesnpx skills add Amatofrancesco99/thoughtweave --skill changesgit clone --depth 1 https://github.com/Amatofrancesco99/thoughtweaveWrote 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/amatofrancesco99/thoughtweave/changes)<a href="https://agentmods.dev/skills/amatofrancesco99/thoughtweave/changes"><img src="https://agentmods.dev/badge/skills/amatofrancesco99/thoughtweave/changes.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.00051 | $0.02207 |
| Opus 5 | $0.00026 | $0.01104 |
| Sonnet 5 | $0.00010 | $0.00441 |
| Haiku 4.5 | $0.00005 | $0.00221 |
Grade A, and why
changes 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/changes
Generate a human-readable explanation of implemented changes. The purpose is communication, not documentation. The audience includes developers, reviewers, managers, and stakeholders.
The skill is a tool for the developer, not a replacement. The developer stays at the centre - every decision about what to document, which trade-offs to highlight, and which risks to accept is driven by the developer's judgement. The skill surfaces information, but the developer decides what matters.
Pre-condition Check
Before any questions, verify that a specification exists for this feature:
- Determine the target folder (ask if not known or inheritable from context).
- Check if
spec.mdexists in that folder. - If
spec.mddoes not exist, refuse to proceed: "A changes document documents what changed relative to a specification. Without a spec, there is no anchor to compare against. Please run /sdd first to create a specification for this feature." - If
spec.mdexists but is incomplete, warn and ask whether to proceed or complete the spec first. - If
spec.mdis complete but lacks documented hidden assumptions, flag this and ask the user to review.
[!IMPORTANT] This check is non-negotiable. The changes skill cannot produce meaningful output without a spec.
Implementation Validation
Before generating the changes document:
- Read the
spec.mdto extract requirements, acceptance criteria, decisions, and constraints. - Inspect the actual implementation (code changes, file modifications, architecture) and verify each maps back to a corresponding item in the spec.
- If requirements from the spec are not addressed, flag them as unimplemented and ask if intentionally dropped.
- If the implementation includes behaviour not covered by the spec, flag it as untracked and ask for justification.
- If
AGENTS.mdexists, validate that the implementation respects its constraints, best practices, and architectural directives. Flag deviations.
Vulnerability Scanning
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 · 199 lines · 51 tokens per session scan A 1818373a7459
changes is a skill published in the GitHub repository Amatofrancesco99/thoughtweave (5 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 2,207 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-31.
Other skills, from other repositories
harness
Route Harness Starter Kit workflows. Use when the user invokes /harness with adopt, doctor, update, refresh, review, or review sub-agent, or asks to apply, diagnose, maintain, or review repository harness guidance.
harness-adopt
Apply Harness Starter Kit prompt-first adoption to a target repository. Use when the user asks to apply, install, adopt, or bootstrap repository harness guidance, checks, memory, and adoption reporting.
harness-refresh
Review stale, duplicated, obsolete, or unused target harness guidance. Use when the user asks for /harness refresh or wants harness maintenance recommendations without default edits.
harness-review
Review the current change set from an opposing harness-engineering perspective. Use when the user asks for /harness review, /harness review sub-agent, or a no-edit harness review.
harness-update
Refresh an adopted target repository from the latest Harness Starter Kit reference. Use when the user asks for /harness update or wants source tracking and selective harness updates.
harness-doctor
Run the diagnostic Harness Doctor workflow. Use when the user asks for /harness doctor, harness score, repository harness readiness, or a no-edit harness health report.