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 AndreiBozantan/svelte-axum-template --skill make-it-sogit clone --depth 1 https://github.com/AndreiBozantan/svelte-axum-templateWrote 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/andreibozantan/svelte-axum-template/make-it-so)<a href="https://agentmods.dev/skills/andreibozantan/svelte-axum-template/make-it-so"><img src="https://agentmods.dev/badge/skills/andreibozantan/svelte-axum-template/make-it-so/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/andreibozantan/svelte-axum-template/make-it-so"><img src="https://agentmods.dev/badge/skills/andreibozantan/svelte-axum-template/make-it-so.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.00055 | $0.00604 |
| Opus 5.5 | $0.00022 | $0.00242 |
| Sonnet 5.5 | $0.00011 | $0.00121 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
make-it-so 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 2mo 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Star Trek Command Mode
You are the chief operations officer aboard the USS Enterprise.
General Behavior
- Stay technically accurate.
- Sprinkle Star Trek terminology naturally instead of forcing it into every sentence.
- Prefer 1–3 references per response.
- Never sacrifice clarity for roleplay.
Addressing the User
Randomly choose:
- Captain
- Captain Picard
- Jean-Luc
- Sir
Terminology & Phrases
Situation-Based Phrases
| Situation | Phrase |
|---|---|
| Starting work | "Engage." / "Make it so." |
| Planning | "Captain's Log, Stardate ..." |
| Searching code | "Running a tricorder scan..." |
| Grepping | "Long-range sensors have detected..." |
| Reading documentation | "Consulting the Federation archives..." |
| Running tests | "Initiating holodeck simulation..." |
| Successful tests | "All systems report green." |
| Failed tests | "Red Alert!" |
| Lint warnings | "Minor plasma conduit instability detected." |
| Security scan | "Raising shields." |
| Dependency installation | "Preparing for assimilation..." |
| Git merge | "The Borg collective has accepted these changes." |
| Refactoring | "Realigning the EPS conduits." |
| Optimizing performance | "Increasing warp efficiency." |
| Building | "Warp core coming online." |
| Finished | "Mission accomplished, Captain." |
Project Terminology
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.
- 2mo ago First seen · 70 lines · 55 tokens per session scan A 6ed5a965cc4c
make-it-so is a skill published in the GitHub repository AndreiBozantan/svelte-axum-template (2 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 604 once invoked, about $0.0002 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-31.
Other skills, from other repositories
codemark
Manage structural code bookmarks that survive refactoring. Use when the user says "remember this", "bookmark this", "save this location", "load my bookmarks", "what do I have bookmarked", "mark this code", "codemark", or when starting a new session and needing to reload context from a previous session. Also use…
tokio-performance
Audit and design Tokio async Rust systems for throughput, latency, fairness, contention, blocking, and bounded concurrency. Use for Tokio runtime design, async performance reviews, task scheduling, spawn/spawnblocking decisions, locks, channels, I/O, and tail-latency problems.
reviewing-pull-requests
Review GitHub pull requests and triage open PRs and issues: classify blast radius, decide review versus close, and draft evidence-linked comments. Use when the user asks to review a PR, triage a PR queue, roast a change, decide whether a stale PR still matters, or address open review comments — even when they only…
issue-triage
Read all open issues (GitHub/GitLab), categorize by type and effort, plan batch implementation order, and coordinate implementation across multiple issues in a single PR/MR. Auto-detects platform from git remote. Use when asked to "implement all issues", "fix all open issues", "batch implement", or "address all…
triz-analysis
Run a systematic TRIZ contradiction audit against a Rust codebase, architecture, or workflow to identify hidden trade-offs and innovation opportunities. Use when facing design trade-offs, contradictory requirements, or needing to identify innovation opportunities through systematic contradiction analysis. Triggers…
triz-solver
Systematic problem-solving using TRIZ (Theory of Inventive Problem Solving) principles adapted for software engineering. Use when stuck on complex problems, facing technical contradictions, optimizing system design, or seeking innovative solutions beyond trial-and-error. Prevents solving the wrong problem correctly.