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/jerrylalala/compound-engineering/sync-tutorialsgit clone --depth 1 https://github.com/Jerrylalala/compound-engineeringWhat 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.00000 | $0.00232 |
| Opus 5 | $0.00000 | $0.00116 |
| Sonnet 5 | $0.00000 | $0.00046 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
sync-tutorials 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 2d 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.
This is a copy
100% identical to sync-tutorials — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Sync Coding Tutor Tutorials
Commit and push your tutorials to the GitHub repository for backup and mobile reading.
Instructions
-
Go to the tutorials repo:
cd ~/coding-tutor-tutorials -
Check for changes: Run
git statusto see what's new or modified -
If there are changes:
- Stage all changes:
git add -A - Create a commit with a message summarizing what was added/updated (e.g., "Add tutorial on React hooks" or "Update quiz scores")
- Push to origin:
git push
- Stage all changes:
-
If no GitHub remote exists:
- Create the repo:
gh repo create coding-tutor-tutorials --private --source=. --push
- Create the repo:
-
Report results: Tell the user what was synced or that everything is already up to date
Notes
- The tutorials repo is at:
~/coding-tutor-tutorials/ - Always use
--privatewhen creating the GitHub repo - This is your personal learning journey - keep it backed up!
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.
- 2d ago First seen · 26 lines · 0 tokens per session scan A cb089a3dba32
sync-tutorials is a command published in the GitHub repository Jerrylalala/compound-engineering (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 232 tokens. A static security scan graded it A with 0 findings. It is 100% identical to sync-tutorials, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
sync-tutorials
Commit and push your tutorials to the GitHub repository for backup and mobile reading.
compose-test
Run Compose UI tests with Espresso. Verify critical user flows.
edit-textbook-chapter
Edit a textbook-style chapter, following evidence-based writing instructions.
explain
Explain code, concepts, or system behavior with adjustable depth levels.
start-1
Claude Code 를 처음 쓰는 PM 이 "설치 → 도구 지도 이해 → CLAUDE.md 로 맥락 주기" 까지 직접 손으로 해보며 익히도록, 한 번에 한 단계씩 끌고 간다.
prep-role
Deep prep for a specific role's interview process. The user wants to know what to expect, how to win, and what kills candidates at their level.