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.
git clone --depth 1 https://github.com/gvkhosla/compound-engineering-piWrote 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/gvkhosla/compound-engineering-pi/sync-tutorials)<a href="https://agentmods.dev/commands/gvkhosla/compound-engineering-pi/sync-tutorials"><img src="https://agentmods.dev/badge/commands/gvkhosla/compound-engineering-pi/sync-tutorials/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/commands/gvkhosla/compound-engineering-pi/sync-tutorials"><img src="https://agentmods.dev/badge/commands/gvkhosla/compound-engineering-pi/sync-tutorials.svg" alt="Reviewed on agentmods" width="80" 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.00232 |
| Opus 5.5 | $0.00000 | $0.00093 |
| Sonnet 5.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 1mo 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- sync-tutorials — 100% identical, 0 lines differ
- sync-tutorials — 100% identical, 0 lines differ
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.
- 1mo ago First seen · 26 lines · 0 tokens per session scan A cb089a3dba32
sync-tutorials is a command published in the GitHub repository gvkhosla/compound-engineering-pi (52 stars, last pushed 15d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
speckit.companion.living-sync
Sync living specs from your current changes — group working-tree changes (uncommitted included) by capability and update every affected spec in one pass (opt-in, update-not-regenerate, never halts).
push-changes
If no topic provided, just document the recent changes. If a topic is provided, focus on documenting that topic.
git-commit
Based on the above changes, create a single git commit. Use the Angular commit message format：.
Checkpoint Commit
Commit changes at meaningful checkpoints throughout the workflow.
commit-push-pr
Commit, push, and open a PR (includes changeset creation).
mach12:push
Commit, push, and post a progress comment using session context or branch detection.