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 bearded-illirian/trailmark --skill tutorial-checkgit clone --depth 1 https://github.com/bearded-illirian/trailmarkWrote 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/bearded-illirian/trailmark/tutorial-check)<a href="https://agentmods.dev/skills/bearded-illirian/trailmark/tutorial-check"><img src="https://agentmods.dev/badge/skills/bearded-illirian/trailmark/tutorial-check/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/bearded-illirian/trailmark/tutorial-check"><img src="https://agentmods.dev/badge/skills/bearded-illirian/trailmark/tutorial-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00102 | $0.01771 |
| Opus 5.5 | $0.00041 | $0.00708 |
| Sonnet 5.5 | $0.00020 | $0.00354 |
| Haiku 4.5 | $0.00010 | $0.00177 |
Grade A, and why
tutorial-check 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.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tutorial-Check Protocol
Homework validator for the QUICKSTART walkthrough. Runs 5 checks against the user's workspace to confirm they set up their first real project correctly. Reports ✅/❌ per step with a one-line remediation hint.
Read-only — never modifies files or DB.
When to invoke
After the user completes the 5-step homework in docs/QUICKSTART.md § 5:
- Create a project named
my-tutorial - Start a task in that project (
/go-start+/go-fast) - Approve the full chain (ok, ok, 1)
- Verify 5 artifact files exist in
tasks/log/{slug}/ - Confirm the task appears in Flow UI
Then the user runs /tutorial-check and gets pass/fail per step.
Step 0 — Detect workspace root
Find the workspace root by walking up from CWD until we find framework.yml
or manifest.yml at the same level. If none found within 5 levels — abort:
⚠️ Not inside a framework workspace. Run this from anywhere inside your
framework directory (where framework.yml lives).
Set {workspace_root} for all subsequent checks.
Step 1 — Run the 5 checks
Each check is independent — a failure in one doesn't skip the others.
Check 1: Project my-tutorial created
test -d "{workspace_root}/projects/my-tutorial" && D1=✅ || D1=❌
grep -q "id: my-tutorial" "{workspace_root}/aihub/projects.yml" && D2=✅ || D2=❌
test -L "{workspace_root}/projects/my-tutorial/.agents/skills" && D3=✅ || D3=❌
Pass = D1 AND D2 AND D3.
Remediation: bash bin/new-project my-tutorial
Check 2: Task started in that project
COUNT=$(sqlite3 "{workspace_root}/tasks/routing.db" \
"SELECT COUNT(*) FROM artifacts WHERE project = 'my-tutorial'")
test "$COUNT" -gt 0 && CHECK2=✅ || CHECK2=❌
Pass = at least one artifact row exists.
Remediation: cd projects/my-tutorial && claude, then /go-start and /go-fast "...".
Check 3: Chain approved (plan-first artifact exists)
COUNT=$(sqlite3 "{workspace_root}/tasks/routing.db" \
"SELECT COUNT(*) FROM task_artifacts ta
JOIN artifacts a ON ta.task_id = a.id
WHERE a.project = 'my-tutorial' AND ta.artifact_type = 'plan-first'")
test "$COUNT" -gt 0 && CHECK3=✅ || CHECK3=❌
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed e8632579d351
- 1mo ago First seen · 217 lines · 102 tokens per session scan A 411dbbaf9fb3
tutorial-check is a skill published in the GitHub repository bearded-illirian/trailmark (19 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 1,771 once invoked, about $0.0004 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
stub_distance_skill
a deterministic stub returned by the override engine in unit tests.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
verification-before-completion
Use when about to claim work is complete, fixed, or passing, or before committing or creating PRs.
qa
Browser-based QA verification. Launches a real browser, navigates the app, clicks buttons, fills forms, and tests user flows. Works as a standalone skill or as a phase end condition in campaigns. Requires Playwright (optional dependency, graceful skip if not installed).