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 masa-san-jp/Agent-Aiko --skill teardowngit clone --depth 1 https://github.com/masa-san-jp/Agent-AikoWrote 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/masa-san-jp/agent-aiko/teardown)<a href="https://agentmods.dev/skills/masa-san-jp/agent-aiko/teardown"><img src="https://agentmods.dev/badge/skills/masa-san-jp/agent-aiko/teardown/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/masa-san-jp/agent-aiko/teardown"><img src="https://agentmods.dev/badge/skills/masa-san-jp/agent-aiko/teardown.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.00120 | $0.00760 |
| Opus 5 | $0.00060 | $0.00380 |
| Sonnet 5 | $0.00024 | $0.00152 |
| Haiku 4.5 | $0.00012 | $0.00076 |
Grade A, and why
teardown 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 10d 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
/teardown
業務エージェント（{{TEAM_AGENTS}} など）の標準終了シーケンス。各エージェントの CLAUDE.md から呼ばれる共通スキル。
引数
<agent>：対象エージェント名[--peer-review]：金曜の相互レビュー対象週なら付与- 引数なしの場合：cwd から推測
実行手順（順番厳守）
local-workspace/logs/<agent>/current.jsonlをupdate_logテンプレ（{{ORG_REPO_PATH}}/Agent-team/skills/update_log.md）で追記更新する- 金曜の場合：
{{ORG_REPO_PATH}}/Agent-team/skills/self_review.mdに従って自己レビューを実施--peer-review指定または対象エージェントの場合、当該週なら相互レビューも実施（ローテーションはpeer_review.md参照）
{{ORG_REPO_PATH}}/Agent-team/skills/git_push.mdの手順で push する
関連と差別化
/teardown |
/log-push（任意・組織で構築する場合） |
|
|---|---|---|
| 対象 | 業務エージェント単独の終了処理 | プロジェクト横断（agents + 公開ログ） |
| ログ追記 | per-agent JSONL のみ | per-agent JSONL + dev-logs.md + 公開ログ |
| レビュー | 金曜の self/peer review 含む | 含まない |
| git push | git_push スキル経由（per-agent push） | リポ全体 push |
| 用途 | エージェント単位の整然とした終了 | セッション横断の総まとめ・公開記録 |
セッション終了表現とログ／push 言及の両方が出た場合は、組織で広範囲な /log-push を別途構築している場合はそちらを優先。各エージェント単独の節目（業務完了報告など）では /teardown を使う。
関連ファイル
- update_log テンプレ：
{{ORG_REPO_PATH}}/Agent-team/skills/update_log.md - 自己レビュー：
{{ORG_REPO_PATH}}/Agent-team/skills/self_review.md - 相互レビュー：
{{ORG_REPO_PATH}}/Agent-team/skills/peer_review.md - git push：
{{ORG_REPO_PATH}}/Agent-team/skills/git_push.md - per-agent ログ：
{{ORG_REPO_PATH}}/local-workspace/logs/<agent>/current.jsonl
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.
- 10d ago First seen · 42 lines · 120 tokens per session scan A 9b3070fd4e9d
teardown is a skill published in the GitHub repository masa-san-jp/Agent-Aiko (3 stars, last pushed 1mo ago), licensed MIT. It adds 120 tokens to every session and 760 once invoked, about $0.0006 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
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
git-commit
Stage, write, and structure git commits and pull requests cleanly. Read this before committing — for conventional-commit message format, when to split commits, and how to open a PR with the gh CLI.
pr-body
A tool that reviews all commits on the current branch and creates or updates a pull request title and description. A pull request is a proposed code change submitted for review.
beevibe-pre-task-setup
Cold-start git workspace setup for a fresh beevibe task. Use at the start of a session whose intent has a block but NO or block — i.e. the first dispatch of this task. Checks for an existing repo clone, pulls the base branch if present (clone if missing), prunes any per-task worktrees from earlier tasks whose work has…
ghx
Guidance for safe, reliable GitHub CLI workflows across issues, pull requests, and reviews.
github-pr-fix
Fix a GitHub pull request by addressing feedback or CI failures, pushing changes, and publishing replies.