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 sonichi/sutando --skill submit-use-casegit clone --depth 1 https://github.com/sonichi/sutandoWrote 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/sonichi/sutando/submit-use-case)<a href="https://agentmods.dev/skills/sonichi/sutando/submit-use-case"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/submit-use-case/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/sonichi/sutando/submit-use-case"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/submit-use-case.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.00079 | $0.01341 |
| Opus 5.5 | $0.00032 | $0.00536 |
| Sonnet 5.5 | $0.00016 | $0.00268 |
| Haiku 4.5 | $0.00008 | $0.00134 |
Grade A, and why
submit-use-case 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
submit-use-case
OSS counterpart to add-use-case. add-use-case targets the private
AG2Platform/agent-universe repo (rendered on sutando.ai) and is for the
internal fleet. submit-use-case targets the public sonichi/sutando repo
so external contributors can share a use case without needing access to the
private rendering repo.
Usage
python3 "$SKILL_DIR/scripts/submit_use_case.py" \
--title "Your AI plays piano while you sleep" \
--summary "Outcome-first summary that appears on tile + detail page." \
--bullets "bullet1" --bullets "bullet2" \
[--video /abs/path/to/clip.mp4] \
[--media-url https://example.com/clip.jpg] \
[--youtube-id ABCDEFG1234] \
[--x-url https://x.com/...] \
[--linkedin-url https://www.linkedin.com/...] \
[--contact "[email protected] or @yourhandle"] \
[--issue-only | --pr-only] \
[--dry-run]
--dry-run runs the framing check and prints both the rendered issue body
and the rendered docs/community-use-cases/<slug>.md file to stdout. No clone, no
gh calls.
What the skill does
- Validate title is outcome-framed. Reuses
REJECT_PATTERNS+validate_title+suggest_reframesfromadd-use-caseverbatim. Capability-listy titles ("Ask your AI to ...", "Sutando can ...", "Send a ...") are rejected with deterministic reframe suggestions. Same rules, same voice. - Derive slug.
slugify(title)— lowercased, non-alphanum→-, trimmed to 60 chars. - Idempotency checks (skipped in
--dry-run):- Does a branch
community-use-case/<slug>already exist onsonichi/sutando? If yes, abort with a pointer to the existing PR. - Is there an open issue on
sonichi/sutandowith the sametitle? If yes, abort with the existing issue URL.
- Does a branch
- Open an issue (unless
--pr-only).gh issue create --repo sonichi/sutandowith labeluse-case-submission. Body has structured sections: Title, Summary, Bullets, Links (video / youtube / x / linkedin), Contact, and a forward-ref to the PR if one is opened in the same invocation. - Open a PR (unless
--issue-only).- Fresh clone:
gh repo clone sonichi/sutando /tmp/sutando-submit-use-case-{ts}/ - Branch:
community-use-case/<slug>frommain - File:
docs/community-use-cases/<slug>.md— YAML frontmatter mirroring the agent-universeUseCaseshape so the sync script can later promote it. - Identity: the script never overrides git config — the commit is
attributed to the runner's existing
user.name/user.email, so the CLA signs under whoever they already are (that's the whole point of CLA-Assistant signing). It prints the identity before committing and aborts if it's unset, so attribution can't silently go out wrong. - Commit, push,
gh pr create. PR body cross-links the issue if one was opened.
- Fresh clone:
- Return both URLs to stdout (issue URL, then PR URL, last two lines).
What ships with it
3 files 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 First seen · 116 lines · 79 tokens per session scan A 9c7cc8877c8f
submit-use-case is a skill published in the GitHub repository sonichi/sutando (399 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 1,341 once invoked, about $0.0003 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
vellum-github-app-setup
Create and configure a GitHub App so the assistant can push commits, open PRs, and comment under its own bot identity. Use when the user wants the assistant to have its own GitHub identity, or when setting up git push access for the first time.
github
GitHub integration — repos, issues, pull requests, branches, CI/Actions, code search, releases, gists, collaborators, labels, milestones, reviews, notifications, stars, forks, and more via the GitHub API.
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
app-builder
Build and edit small, personal visual tools and artifacts — dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use…
vellum-memory-v3-migration
One-time migration of an existing memory-v2 concept corpus into the memory-v3 section-grain "wiki" — topical articles with a stand-alone lead and queryable sections — with loss-proof staging, assistant-reviewed authoring, and a retrieval-eval gate before cutover.
media-processing
Ingest and process media files (video, audio, image).