Borrowing it
Nothing to install: this file belongs to sturlese/stigmergy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sturlese/stigmergy/main/.claude/skills/land-a-change/SKILL.mdgit clone --depth 1 https://github.com/sturlese/stigmergyWrote 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/sturlese/stigmergy/land-a-change)<a href="https://agentmods.dev/skills/sturlese/stigmergy/land-a-change"><img src="https://agentmods.dev/badge/skills/sturlese/stigmergy/land-a-change/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/sturlese/stigmergy/land-a-change"><img src="https://agentmods.dev/badge/skills/sturlese/stigmergy/land-a-change.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.00026 | $0.00472 |
| Opus 5 | $0.00013 | $0.00236 |
| Sonnet 5 | $0.00005 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
land-a-change 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 12d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Land a Stigmergy change
Read CLAUDE.md and the active implementation specification before changing behavior. Use code
and tests as the authority when older prose conflicts with them.
Select the workflow
| Change | Workflow |
|---|---|
| Observable defect or false executable promise | squad:fix |
| New capability or moved product surface | squad:define then squad:build |
| Behavior-preserving restructuring | squad:refactor |
| Documentation-only correction | ordinary change closed by squad:review |
Read squad:breaking-change before changing a public tool contract, schema, persisted format, or
event shape. The current test deployment uses a clean cut: do not add migration, compatibility, or
rollback machinery unless a later specification explicitly requires it.
Use an independent security/architecture auditor when the change touches ACL decisions, identity or token resolution, queue leasing or retries, Git gates, evidence storage, answer verification, or any read path that can reveal restricted knowledge.
Keep both repositories coherent
Changes to the filing contract normally affect both the platform and the knowledge repository. Update the live librarian skill, thin linter/authorship launchers, templates, control files, and workflows with the platform code and fixtures. The platform package owns the executable contract; the knowledge repository must not carry a second implementation.
Model-owned knowledge paths are committed by the trusted writer identity and pushed through the librarian GitHub App. Operator-owned controls and documentation use the normal contributor identity. Both repositories must pass their own CI.
Completion
- Run focused tests, Ruff, and the complete keyless suite.
- Run the proportional final-validation workflow and resolve every finding.
- Commit and push both repositories with the required identities; wait for green CI.
- Deploy every affected process group.
- Follow
validate-deploymentfor live evidence when the image or cross-system contract changed.
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.
- 12d ago First seen · 50 lines · 26 tokens per session scan A 822211ab206a
land-a-change is a skill published in the GitHub repository sturlese/stigmergy (9 stars, last pushed 17d ago), licensed Apache-2.0. It adds 26 tokens to every session and 472 once invoked, about $0.0001 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
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
hyalo-changelog
Maintain Keep a Changelog files with Hyalo's changelog profile and add/release commands.
memobase
A Russian-language skill for searching a local knowledge base built from documents and other sources such as web pages, YouTube, audio, and Obsidian notes.
knowsift
Compile collected videos, articles, documents, and research into layered, traceable knowledge documents or fail-closed claim certificates. Use when a user needs research synthesis that separates supported knowledge, conditional findings, practitioner experience, viewpoints, anecdotes, disputes, and rejected claims; do…
kb-log
A skill for recording important technical decisions and debugging lessons in a team knowledge base or a local ledger file.
kb-brief
A project-start briefing that searches a team's knowledge base for past pitfalls, decisions, recent changes, and people familiar with the work. It is intended for new tasks, issues, and bug fixes.