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 LeeYudok/agents-scaffold --skill statusgit clone --depth 1 https://github.com/LeeYudok/agents-scaffoldWrote 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/leeyudok/agents-scaffold/status)<a href="https://agentmods.dev/skills/leeyudok/agents-scaffold/status"><img src="https://agentmods.dev/badge/skills/leeyudok/agents-scaffold/status.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.00044 | $0.00845 |
| Opus 5 | $0.00022 | $0.00423 |
| Sonnet 5 | $0.00009 | $0.00169 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
status 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 7d 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
프로젝트 상태 조회
실행 순서 (병렬로)
1. Git 상태
git status --short
git log --oneline -5
git branch -a | grep -v remotes | head -10
2. 빌드 상태 (스택 감지)
# package.json 있으면
[ -f package.json ] && (
echo "=== TypeScript ===" && (bunx tsc --noEmit 2>&1 | tail -5 || npx tsc --noEmit 2>&1 | tail -5)
echo "=== 빌드 ===" && (bun run build 2>&1 | tail -5 || npm run build 2>&1 | tail -5)
) || true
# go.mod 있으면
[ -f go.mod ] && echo "=== Go build ===" && go build ./... 2>&1 | tail -5 || true
# Cargo.toml 있으면
[ -f Cargo.toml ] && echo "=== Cargo check ===" && cargo check 2>&1 | tail -5 || true
# build.gradle 있으면
[ -f build.gradle ] || [ -f build.gradle.kts ] && echo "=== Gradle ===" && ./gradlew compileJava 2>&1 | tail -5 || true
3. 테스트 현황
# 가장 최근 테스트 결과 (있으면)
find . -name "*.xml" -path "*/test-results/*" -newer package.json 2>/dev/null | head -3
4. 미완료 이슈 (GitLab)
command -v glab >/dev/null && glab issue list --state=opened -P 1 --per-page 5 2>/dev/null || true
5. 프로세스 상태 (pm2/포트)
command -v pm2 >/dev/null && pm2 list 2>/dev/null | head -20 || true
6. 오늘 사용량 (옵션 — ccusage 가 있을 때만)
# ccusage 는 Claude Code 전용 사용량 도구다. 설치돼 있지 않으면 조용히 건너뛴다
# (Codex·agy 등 다른 하네스에서는 해당 없음).
command -v ccusage >/dev/null && ccusage daily --since "$(date +%Y%m%d)" --json 2>/dev/null \
| python3 -c "import json,sys; d=json.load(sys.stdin).get('daily') or [{}]; r=d[0]; print(f\"오늘 {r.get('totalTokens',0):,} 토큰 / \${r.get('totalCost',0):.2f}\")" 2>/dev/null || true
출력 형식
## 프로젝트 상태 — {{PROJECT_NAME}} (YYYY-MM-DD HH:MM:SS)
### Git
브랜치: feature/issue-42-xxx
변경: 3 modified, 1 untracked
최근 커밋: abc1234 fix: ...
### 빌드
TypeScript: ✅ 에러 없음 / ❌ N개 에러
빌드: ✅ 성공 / ❌ 실패
### 이슈 (오픈)
#42 [feature] ...
#38 [bug] ...
### 사용량 (ccusage 있을 때만)
오늘 1,207,480,323 토큰 / $1227.00
### 다음 할 일
- (현재 브랜치 기준 TODO 코멘트나 남은 작업)
Learned warnings
(실행 중 발견한 주의사항이 여기에 누적됩니다)
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.
- 7d ago First seen · 88 lines · 44 tokens per session scan A fc19998c97d4
status is a skill published in the GitHub repository LeeYudok/agents-scaffold (25 stars, last pushed 8d ago), licensed MIT. It adds 44 tokens to every session and 845 once invoked, about $0.0002 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-30.
Other skills, from other repositories
memstack-security-git-guard
Use when the user says 'git-guard', 'check git protection', 'is this repo protected', 'verify gitleaks', 'set up git hooks', 'install git-guard', or wants to confirm a repo blocks secrets and internal files before commit. This is an installer and verifier, NOT a scanner (gitleaks does the actual scanning). Do NOT use…
memstack-development-changelog-generator
Use when the user says 'generate changelog', 'update changelog', 'what changed', 'release notes', 'write changelog', or needs a formatted CHANGELOG.md from git commit history. Do NOT use for diary entries, git log viewing, or commit message writing.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
memstack-security-secrets-scanner
Use this skill when the user says 'scan for secrets', 'check for leaked keys', 'secrets scanner', 'hardcoded credentials', 'API key leak', or needs to detect exposed secrets in source code. Do NOT use for dependency vulnerabilities or RLS auditing.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.