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 josephfung/trimkit --skill sysopsgit clone --depth 1 https://github.com/josephfung/trimkitWrote 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/josephfung/trimkit/sysops)<a href="https://agentmods.dev/skills/josephfung/trimkit/sysops"><img src="https://agentmods.dev/badge/skills/josephfung/trimkit/sysops/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/josephfung/trimkit/sysops"><img src="https://agentmods.dev/badge/skills/josephfung/trimkit/sysops.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.00039 | $0.00604 |
| Opus 5.5 | $0.00016 | $0.00242 |
| Sonnet 5.5 | $0.00008 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
sysops 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sysops
If the first word of the argument is log or learnings, handle it directly — do NOT delegate to the sysops subagent.
/sysops log
Parse the argument:
/sysops log→ show last 10 entries across all deployments/sysops log <Deployment>→ show last 10 entries for that deployment (case-insensitive match)/sysops log <Deployment> --last <N>→ show last N entries for that deployment
Run this command, substituting <deployment> (omit --deployment entirely if no deployment was given) and <N> (default 10):
trimkit-sysops-log-search --human [--deployment "<deployment>"] [--last <N>]
If trimkit-sysops-log-search is not on PATH, tell the user:
trimkit-sysops-log-searchis not installed. Runinstall.shfrom your trimkit directory to set it up.
If trimkit-sysops-log-search is found but exits non-zero, show the user the error output and suggest checking file permissions on ~/.claude/sysops/audit.jsonl.
/sysops learnings
Parse the argument:
/sysops learnings→ show all stored learnings across all deployments (deduplicated)/sysops learnings <Deployment>→ show learnings for that deployment only (case-insensitive match)
Run this command, substituting <deployment> (omit --deployment entirely if no deployment was given):
trimkit-learnings-search --human [--deployment "<deployment>"]
If trimkit-learnings-search is not on PATH, tell the user:
trimkit-learnings-searchis not installed. Runinstall.shfrom your trimkit directory to set it up.
If trimkit-learnings-search is found but exits non-zero, show the user the error output and suggest checking file permissions on ~/.claude/sysops/learnings.jsonl.
Otherwise, delegate to the sysops subagent using the Agent tool.
Pass the user's argument directly as the prompt. If no argument was given, default to a status check across all deployments.
Examples:
/sysops→ prompt: "Check the status of all my servers"/sysops status→ prompt: "Check the status of all my servers"/sysops update Pulse→ prompt: "Update Pulse"/sysops update my servers→ prompt: "Update all my servers"
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 · 60 lines · 39 tokens per session scan A af9608ee385b
sysops is a skill published in the GitHub repository josephfung/trimkit (3 stars, last pushed 1mo ago), licensed MIT. It adds 39 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
stack-baseline
The pinned default technology stack for SMB Product-Builder products. One source of truth so the architect, app-scaffolder, auth-engineer, and senior-dev never re-decide the stack per build — they build ON it. Covers framework, ORM/DB, auth, UI, payments/email/SMS, files, jobs, testing, hosting, and observability…
deploy-landed
A deployment verification procedure that checks whether the intended code revision is actually running, its environment settings are present, and the product works. A deployment is the process of putting new software on a server or hosting platform.
observability-baseline
Scaffold-time observability so a shipped product is not blind in prod from day one — error capture (Sentry), request-id structured logging, and /healthz + /readyz endpoints. stack-baseline pins Sentry but nothing wires it; this is the wiring. Loaded by app-scaffolder (bake into the scaffold), infra-provisioner (prod…
dynamic-workflow-patterns
Pattern taxonomy, agent role combinations, model routing, unit-of-work sizing, review-findings settling, and resilience discipline for Claude Code dynamic workflows. ALWAYS load this skill before authoring or running any Workflow tool script, and ALWAYS load it when the user mentions "workflow" or "ultracode" in any…
serena-tool-selection
Mandatory tool-selection protocol for Serena LSP tools (mcpserena) versus the Claude Code built-in Grep, Search, Read, and Edit tools for code inside the project Serena serves: which Serena tool answers each navigation or editing task, how to load deferred Serena tool schemas, name-path and relative-path conventions…
deploy
This skill activates automatically when the task involves.