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 auto-syncgit 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/auto-sync)<a href="https://agentmods.dev/skills/insajin/autopus-adk/auto-sync"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/auto-sync/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/auto-sync"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/auto-sync.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.00021 | $0.02462 |
| Opus 5.5 | $0.00008 | $0.00985 |
| Sonnet 5.5 | $0.00004 | $0.00492 |
| Haiku 4.5 | $0.00002 | $0.00246 |
Grade A, and why
auto-sync 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.
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
auto-sync — 문서 동기화 스킬
OMP Invocation
/auto sync .../auto-sync ...- Load detail skill
auto-syncfor either entrypoint.
프로젝트: autopus-adk | 모드: full
설명
구현 완료 후 코드와 문서를 동기화합니다.
사용법
/auto-sync SPEC-ID
/auto-sync
OMP 기본 실행 모델
- OMP에서는
sync도 기본적으로taskbatch 기반 subagent-first를 따릅니다. - 메인 세션은 동기화 범위 결정, 최종 상태 갱신, 커밋 판단을 담당합니다.
- 변경점 검토, 문서 영향 분석, 검증 로그 정리는 필요 시 서브에이전트로 위임합니다.
- 사용자가
--auto또는--solo를 명시하지 않았고 현재 OMP 런타임 정책이 암묵적taskbatch 호출을 제한하면, 진행을 멈추고 하네스 기본값과 제약을 명시한 뒤 서브에이전트 opt-in 또는--solo확인을 먼저 받아야 합니다. - 변경 범위가 작으면 메인 세션에서 직접 마무리할 수 있습니다.
동기화 항목
- SPEC 상태 → completed
- API 문서 갱신
- 아키텍처 다이어그램 업데이트
- Lore 의사결정 기록
- CHANGELOG 갱신
- Lore 형식 자동 커밋
구조 문서 동기화
구조 변경이 감지되면 다음 문서를 함께 갱신합니다.
ARCHITECTURE.md.autopus/project/structure.md.autopus/project/tech.md.autopus/project/product.md.autopus/project/workspace.md
특히 repo 경계, 빌드/릴리스 스크립트, desktop/browser/API surface가 바뀌면 workspace.md의 QA/Journey Pack 대상 리포와 auto qa init --project-dir <repo> 명령도 함께 갱신합니다. meta workspace의 root .autopus/qa/**는 runtime/generated evidence로 취급하고 제품 리포 Journey Pack 위치와 섞지 않습니다.
@AX Lifecycle Management
동기화 시 코드베이스의 @AX 태그 수명주기를 관리합니다.
TODO Cycle Tracking
@AX:TODO태그를 찾습니다.@AX:CYCLE:N카운터를 증가시키거나 없으면@AX:CYCLE:1을 추가합니다.- CYCLE이 3 이상이면
@AX:WARN으로 승격하고 이유를 기록합니다.
ANCHOR Fan-In Verification
@AX:ANCHOR태그를 찾습니다.- 함수 참조 수를 grep 기반으로 점검합니다.
- caller count가 3 미만이면
@AX:NOTE로 내리고 이유를 갱신합니다.
NOTE Cleanup
- 특정 함수/심볼을 참조하는
@AX:NOTE를 찾습니다. - 해당 함수/심볼이 아직 존재하는지 확인합니다.
- orphan NOTE는 제거합니다.
품질 게이트
- 에러: 0 / 경고: 최대 10
Lore 커밋
동기화 완료 후 변경 파일을 Lore 형식으로 자동 커밋합니다.
- SPEC-ID가 있으면:
docs(<scope>): sync SPEC-{ID} 문서 및 상태 갱신 - SPEC-ID가 없으면:
docs(sync): 프로젝트 문서 동기화 - 구현 코드 포함 시 SPEC 주요 타입(feat, fix 등) 사용
- 변경 사항 없으면 커밋 생략
2-Phase Commit
- Module repo 커밋:
{TARGET_MODULE}내부 SPEC 및 모듈 변경 - Meta repo 커밋: 루트 문서(
ARCHITECTURE.md,.autopus/project/,CHANGELOG.md)
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 · 215 lines · 21 tokens per session scan A 0e057835c81b
auto-sync is a skill published in the GitHub repository Insajin/autopus-adk (111 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 2,462 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
api-interface-design
Use when designing public APIs, module boundaries, provider adapters, tool schemas, or data contracts.
explore
Explore the codebase and summarize how the project is wired.
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…