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 agentmods add commands/dachivadachkoria/claude-code-starter-kit/monitorgit clone --depth 1 https://github.com/dachivadachkoria/claude-code-starter-kitWrote 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/commands/dachivadachkoria/claude-code-starter-kit/monitor)<a href="https://agentmods.dev/commands/dachivadachkoria/claude-code-starter-kit/monitor"><img src="https://agentmods.dev/badge/commands/dachivadachkoria/claude-code-starter-kit/monitor.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 | $0.00013 | $0.01370 |
| Opus 5 | $0.00006 | $0.00685 |
| Sonnet 5 | $0.00003 | $0.00274 |
| Haiku 4.5 | $0.00001 | $0.00137 |
Grade A, and why
monitor 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 3d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Health Monitor
Analyze repository health and identify maintenance tasks.
Target: $ARGUMENTS (default: full repository scan)
Health Checks
1. Dependency Health
# Check for outdated dependencies
# Python
pip list --outdated 2>/dev/null | head -20
# JavaScript
npm outdated 2>/dev/null | head -20
# Go
go list -u -m all 2>/dev/null | grep '\[' | head -20
Assess:
- Major version updates available
- Security patches needed
- Deprecated packages in use
- Unused dependencies
2. Code Quality Metrics
# Line count and complexity
find . -name "*.py" -o -name "*.js" -o -name "*.go" | head -100 | xargs wc -l 2>/dev/null | tail -1
# TODO/FIXME count
grep -rn "TODO\|FIXME\|HACK\|XXX" --include="*.py" --include="*.js" --include="*.go" . 2>/dev/null | wc -l
Track:
- Files over 500 lines (candidates for splitting)
- Functions over 50 lines (complexity concern)
- Cyclomatic complexity hotspots
- Code duplication
3. Test Health
# Test count
find . -name "test_*.py" -o -name "*.test.js" -o -name "*_test.go" | wc -l
# Recent test failures (if CI logs available)
Assess:
- Test coverage percentage
- Flaky test patterns
- Missing test directories
- Test execution time trends
4. Documentation Status
Check:
- README.md completeness
- API documentation currency
- Docstring coverage
- Changelog updates
5. Git Health
# Large files
git rev-list --objects --all | git cat-file --batch-check='%(objecttype) %(objectname) %(objectsize) %(rest)' | awk '/^blob/ {print $3, $4}' | sort -rn | head -10
# Stale branches
git branch -r --merged origin/main | grep -v main | head -10
# Recent commit activity
git log --oneline --since="30 days ago" | wc -l
Track:
- Large files that shouldn't be in git
- Stale branches to clean up
- Commit frequency trends
- Contributors activity
6. Security Posture
Quick checks:
.envfiles in.gitignore- No hardcoded secrets in recent commits
- Dependency vulnerabilities
- Security headers in configs
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.
- 3d ago First seen · 209 lines · 13 tokens per session scan A 635493e2926e
monitor is a command published in the GitHub repository dachivadachkoria/claude-code-starter-kit (4 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 1,370 once invoked, about $0.0001 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 commands, from other repositories
fix-issue
이슈 #$ARGUMENTS 를 처리한다(이슈 우선 워크플로).
set-tracker
Set the issue tracker for the current project.
maggy-init
Interactive wizard that configures Maggy for the user's org, issue tracker, and codebases. Writes /.maggy/config.yaml and ensures deps are installed.
resume-project
Cold-start project — BOARD, PROGRESS, stalled tasks, worktrees.
specmanager-build
Build one phase of a SpecManager feature's plan via the builder subagent. Stops at the phase boundary; never advances.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.