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 JasonColapietro/suede-creator-skills --skill suede-ops-assessmentgit clone --depth 1 https://github.com/JasonColapietro/suede-creator-skillsWrote 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/jasoncolapietro/suede-creator-skills/suede-ops-assessment)<a href="https://agentmods.dev/skills/jasoncolapietro/suede-creator-skills/suede-ops-assessment"><img src="https://agentmods.dev/badge/skills/jasoncolapietro/suede-creator-skills/suede-ops-assessment/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/jasoncolapietro/suede-creator-skills/suede-ops-assessment"><img src="https://agentmods.dev/badge/skills/jasoncolapietro/suede-creator-skills/suede-ops-assessment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high YARA Match · line 3 YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
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.00197 | $0.02801 |
| Opus 5 | $0.00098 | $0.01401 |
| Sonnet 5 | $0.00039 | $0.00560 |
| Haiku 4.5 | $0.00020 | $0.00280 |
Grade A, and why
suede-ops-assessment 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 9d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Suede Ops Assessment
Iron law: map the floor, not the org chart.
Every operation has two maps. The leadership map describes how the business is meant to run. The floor map describes how the work actually gets done, including each workaround, each unofficial spreadsheet, and each extra step that exists because something broke once. A system designed from the leadership map gets routed around, because the people doing the work can feel the mismatch on day one.
This skill produces the floor map and the numbers attached to it. It stops before deciding what to build.
The requester's numbers are given
Their hours, costs, volumes, error rates, and history are inputs, not claims to audit. No step here verifies, scores, hedges, or gates on a figure the requester supplied.
What does get audited is anything this skill produces: a benchmark it
reached for, an estimate it filled in, a process step it inferred rather than
heard. Mark every one of those inline as [assumed] and list them in the Output
Contract, so a reader can tell the operation's own numbers from this skill's.
Never substitute an industry average for a number the requester has. Ask for theirs, or record the line as missing.
Before Starting
- Scope — which processes, departments, or surfaces are in the assessment.
- Access — what the requester has authorized you to read. Work inside it.
- Who does the work — names or roles per process, separated into people who perform it and people who manage it.
- Self-applied or on behalf — a founder assessing their own operation reads Step 5 differently from an outside team assessing a client's.
Read references/interview-guide.md before the first interview.
Step 1 — Interview the floor
Interview at least one person per process who performs it, not only the person who manages it. Where the two descriptions differ, record both and mark the performer's version as the floor map.
Run it as a walkthrough rather than a survey: the question is what happens next, repeated until the process ends. The guide carries the full question bank; these four earn their place in every interview.
What ships with it
4 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.
- 9d ago First seen · 264 lines · 197 tokens per session scan A 2fe1d9315262
suede-ops-assessment is a skill published in the GitHub repository JasonColapietro/suede-creator-skills (135 stars, last pushed today), licensed MIT. It adds 197 tokens to every session and 2,801 once invoked, about $0.0010 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-09-03.
Other skills, from other repositories
after-action-report
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event.…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
mass-ulw
Drives dependency-ordered child work through the native workflow tool, one run per phase with retry/amend/send recovery. Use when the user asks for mass-ulw, a DAG of tasks, or fan-out work where some tasks must wait on others.
beta-program-management
Running closed and open betas that produce real signal. Beta participant selection, structured feedback collection, beta-to-GA decision criteria, and the difference between soft-launch (no structure, no signal), kitchen-sink (everyone in, no actionable feedback), and structured beta (calibrated cohort, intentional…
okr-design
OKR design as actually shipped, not as conference-talk theory. Outcome statements that drive decisions, key results that measure the right thing, scoring discipline, mid-quarter recalibration, and the difference between sandbagged OKRs (always 100%) and aspirational OKRs (always 30%) and stretch OKRs (genuine ambition…
roadmap-planning
Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next…