Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Flagrare/llm-tutor/plugin install llm-tutorWrote 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/flagrare/llm-tutor/tutor-statusline-toggle)<a href="https://agentmods.dev/skills/flagrare/llm-tutor/tutor-statusline-toggle"><img src="https://agentmods.dev/badge/skills/flagrare/llm-tutor/tutor-statusline-toggle.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.1 | $0.00096 | $0.00386 |
| Opus 5 | $0.00048 | $0.00193 |
| Sonnet 5 | $0.00019 | $0.00077 |
| Haiku 4.5 | $0.00010 | $0.00039 |
Grade A, and why
tutor-statusline-toggle 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 7d 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.
What it actually says
Tutor Statusline Toggle
This skill flips the visibility flag for llm-tutor's statusline segment. The wrapper stays installed either way — toggling is the lightweight on/off, uninstall is the full removal.
Step 1 — Run the toggle script
Pass the user's argument through unchanged (on / off / empty for cycle).
bash "$CLAUDE_PLUGIN_ROOT/scripts/statusline-toggle.sh" $ARGUMENTS
Echo the script's output.
Step 2 — One-line context for the user
If the user toggled off and the wrapper is currently installed:
"Original statusline renders unchanged. Run
/tutor-statusline-toggle onto bring the segment back."
If the user toggled on and the wrapper isn't installed yet (the script's output will warn about this), suggest:
"Run
/tutor-statusline-installfirst — the toggle is set, but nothing's wrapping the statusline yet so nothing changes visually."
Hard rules
- Don't run install from this skill. Toggle and install are intentionally separate — the user might want the wrapper installed but the segment hidden (e.g., during a screen-share).
- Don't modify settings.json. The flag is a file under
~/.claude/llm-tutor/, not a settings key.
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.
- 7d ago First seen · 40 lines · 96 tokens per session scan A 055163977aea
tutor-statusline-toggle is a skill published in the GitHub repository Flagrare/llm-tutor (5 stars, last pushed 3mo ago), licensed MIT. It adds 96 tokens to every session and 386 once invoked, about $0.0005 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 skills, from other repositories
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
collaboration-platform-administration
Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and routing, phishing and spam controls, shared mailboxes and distribution groups, external sharing and guest access, permission sprawl in file storage, and retention and legal…
onboarding-and-offboarding
Designs the joining and leaving experience — first-day readiness, ramp to productivity, knowledge capture, and clean exits. Use this to design or fix onboarding, shorten time to productivity, structure a leaver process, capture knowledge before someone leaves, or coordinate the access and asset steps around a joiner…
structure-swift-sources
Organize Swift source trees and oversized Swift files by feature, layer, and declaration group; split large files, normalize // MARK: sections, enforce plain-language block-comment file headers, and move TODO and FIXME text into ledger files. Use after format-swift-sources has established a clean formatting baseline.
tips-helpviewer-workflow
Discover local user-guide topics for installed Apple Mac apps through the Tips HelpViewer catalog, with app matching, installed-version capture, result verification, and authoritative fallback routing. Use when Codex needs task-specific help for an installed Apple app, needs to find a menu command through local Help…
ws
Create and run workstations - permanent areas for routine, repeated work (independent of projects). Actions - new WS, new subWS, new area, new routine, run, from project, list, overview. Hierarchy depth (2 or 3 levels) is fixed at creation.