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/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/leeyudok/agents-scaffold/status"><img src="https://agentmods.dev/badge/skills/leeyudok/agents-scaffold/status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium MCP Rug Pull · line 22 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00930 |
| Opus 5.5 | $0.00018 | $0.00372 |
| Sonnet 5.5 | $0.00009 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
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 27d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
프로젝트 상태 조회
실행 순서 (병렬로)
1. Git 상태
git status --short
git log --oneline -5
git branch -a | grep -v remotes | head -10
2. 빌드 상태 (스택 감지)
# package.json 있으면 — 러너는 하나만 고른다(`a | tail || b` 는 tail 의 종료코드라 폴백이 돌지 않는다)
if [ -f package.json ]; then
if command -v bun >/dev/null; then tsc="bunx tsc"; build="bun run build"; else tsc="npx tsc"; build="npm run build"; fi
echo "=== TypeScript ===" && $tsc --noEmit 2>&1 | tail -5
echo "=== 빌드 ===" && $build 2>&1 | tail -5
fi
# go.mod 있으면
if [ -f go.mod ]; then echo "=== Go build ==="; go build ./... 2>&1 | tail -5; fi
# Cargo.toml 있으면
if [ -f Cargo.toml ]; then echo "=== Cargo check ==="; cargo check 2>&1 | tail -5; fi
# build.gradle 있으면
if [ -f build.gradle ] || [ -f build.gradle.kts ]; then echo "=== Gradle ==="; ./gradlew compileJava 2>&1 | tail -5; fi
3. 테스트 현황
# 가장 최근 테스트 결과 (있으면)
find . -path ./node_modules -prune -o -path "*/test-results/*" -name "*.xml" -print 2>/dev/null | head -3
4. 미완료 이슈 (forge 는 rules/forge.md 기준)
command -v gh >/dev/null && gh issue list --state open --limit 5 2>/dev/null || true # GitHub
command -v glab >/dev/null && glab issue list --per-page 5 2>/dev/null || true # GitLab (기본값이 opened)
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 코멘트나 남은 작업)
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.
- 27d ago Changed · +2 lines 68ca910f769f
- 1mo ago First seen · 88 lines · 44 tokens per session scan A fc19998c97d4
status is a skill published in the GitHub repository LeeYudok/agents-scaffold (36 stars, last pushed 3d ago), licensed MIT. It adds 44 tokens to every session and 930 once invoked, about $0.0002 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
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.
bitbucket-workflow
Bitbucket best practices for pull requests, Pipelines CI/CD, Jira integration, and Atlassian ecosystem workflows.
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
gitlab-workflow
GitLab best practices for merge requests, CI/CD pipelines, issue tracking, and DevOps workflows.
git-workflow
Git conventions and workflow guidelines using Conventional Commits, branching strategies, and best practices for version control.