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 Insajin/autopus-adk --skill hash-anchored-editgit clone --depth 1 https://github.com/Insajin/autopus-adkWrote 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/insajin/autopus-adk/hash-anchored-edit)<a href="https://agentmods.dev/skills/insajin/autopus-adk/hash-anchored-edit"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/hash-anchored-edit/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/insajin/autopus-adk/hash-anchored-edit"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/hash-anchored-edit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 7 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00018 | $0.00530 |
| Opus 5 | $0.00009 | $0.00265 |
| Sonnet 5 | $0.00004 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
hash-anchored-edit 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
Hash-Anchored Edit Skill
파일 수정 전 SHA256 해시로 무결성을 검증하여 충돌 없이 안전하게 수정하는 스킬입니다.
핵심 개념
왜 해시 앵커가 필요한가?
병렬 에이전트 환경에서 동일 파일에 여러 에이전트가 접근할 경우:
- 에이전트 A가 읽은 후 에이전트 B가 수정
- 에이전트 A가 구버전 기반으로 수정 → 충돌 또는 유실
해시 앵커는 파일 상태를 고정하여 이를 방지합니다.
해시 앵커 적용 절차
1단계: 현재 상태 기록
# 수정 전 해시 계산
sha256sum target_file.go > target_file.go.hash
2단계: 수정 전 검증
# 수정 시도 전 해시 비교
sha256sum -c target_file.go.hash
# 성공: target_file.go: OK
# 실패: 파일이 변경되었음 — 재읽기 필요
3단계: 수정 실행
검증 성공 시에만 수정을 진행합니다.
4단계: 수정 후 해시 갱신
sha256sum target_file.go > target_file.go.hash
Edit 도구와의 통합
Edit 도구 사용 시 내장 충돌 감지:
old_string: <정확한 현재 내용>
new_string: <새로운 내용>
old_string이 현재 파일에 없으면 에러 → 재읽기 후 재시도
멀티 에이전트 파일 락
팀 모드에서 파일 소유권 분리:
# 에이전트별 파일 소유권
file_ownership:
backend-dev: ["**/*.go", "!**/*_test.go"]
tester: ["**/*_test.go"]
frontend-dev: ["**/*.ts", "**/*.tsx"]
소유권 외 파일 수정은 금지 → 자동 충돌 방지
주의 사항
.hash파일은 임시 파일 — 커밋하지 않음- 해시 불일치 시 브루트포스 재시도 금지 (최대 3회)
- 3회 실패 시 팀 리드에게 보고
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 · 72 lines · 18 tokens per session scan A 7a80d99215d0
hash-anchored-edit is a skill published in the GitHub repository Insajin/autopus-adk (111 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 530 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-09-03.
Other skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
deploy-local
End-to-end local deployment loop for Gitea-hosted projects. Use when the user wants to commit on dev, push to remote, monitor the golden CI/build/deploy workflow, validate prod on the configured prod host, and fix lint/test/pipeline failures until deployment is healthy.
github-issues
Create well-structured GitHub issues with proper labels, descriptions, and acceptance criteria. Use when creating bug reports, feature requests, or tracking tasks.
git-commit
Create well-structured conventional commit messages following Conventional Commits standard. Use when committing changes, preparing PRs, or generating changelogs.
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification.
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.