Borrowing it
Nothing to install: this file belongs to masa-san-jp/Agent-Aiko. 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/masa-san-jp/Agent-Aiko/main/.claude/skills/dev-check/SKILL.mdgit 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/dev-check)<a href="https://agentmods.dev/skills/masa-san-jp/agent-aiko/dev-check"><img src="https://agentmods.dev/badge/skills/masa-san-jp/agent-aiko/dev-check.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.1 | $0.00000 | $0.00631 |
| Opus 5 | $0.00000 | $0.00316 |
| Sonnet 5 | $0.00000 | $0.00126 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
dev-check 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 6d 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
/dev-check — 三層分離チェックスキル
コミット・push 前に三層分離の整合性を検証します。
前提:開発ログ・設計メモは ../Agent-Lab/Agent-team/agents/aiko/dev-docs/ で管理されていること。
チェック項目
1. claude-code/template/ スキャン(配布用の汚染チェック)
grep -rnE "dev-docs|Agent-Lab" claude-code/template/ --include="*.md" --include="*.sh" --include="*.json" \
| sed -E 's|https?://[^[:space:]"<>)]+||g' \
| grep -E "dev-docs|Agent-Lab"
- ローカルパス参照として
dev-docsまたはAgent-Labが含まれていれば NG(push ブロック対象) - 開発者固有のパス・ツールが含まれていれば NG
- 許容されるのは
https?://の公開アセット URL のみ。URL を一旦除去した上で再度マッチさせるため、file://等のローカル依存 URL や、URL とローカルパスが同じ行に混在するケースもローカル参照は確実に検出される(template-check.shと同じロジック)
2. dev-log.jsonl の更新確認
../Agent-Lab/Agent-team/agents/aiko/dev-docs/dev-log.jsonlの最終行のtsフィールドが今日の日付か確認- 更新されていなければ
/dev-logの実行を促す
3. Agent-Lab 側 dev-docs/README.md の整合確認
../Agent-Lab/Agent-team/agents/aiko/dev-docs/内の実ファイル一覧と README のテーブルを照合- ファイルの追加・削除・リネームが README に反映されていなければ NG
実行タイミング
git commitまたはgit pushの前- セッション終了時
出力形式
=== /dev-check ===
[OK] claude-code/template/ に dev-docs / Agent-Lab 参照なし
[OK] dev-log.jsonl: 今日(YYYY-MM-DD)更新済み
[WARN] ../Agent-Lab/Agent-team/agents/aiko/dev-docs/README.md: 未反映ファイルあり → <ファイル名>
問題があれば修正手順を添えて報告し、ユーザーの確認を得てから push を続行してください。
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.
- 6d ago First seen · 46 lines · 0 tokens per session scan A 5b3ef8e62b78
dev-check is a skill published in the GitHub repository masa-san-jp/Agent-Aiko (3 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 631 tokens. 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
分析当前分支的全部变更,自动生成或更新 PR 标题和正文。聚焦内容质量:解释 why、归纳 what、标注测试方式,遵循 anolisa 项目 PR 模板规范。适用于新建 PR 前生成描述,或已有 PR 需要更新描述。.
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.