Borrowing it
Nothing to install: this file belongs to smartsheet/smartsheet-sdk-tests. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/smartsheet/smartsheet-sdk-tests/mainline/.claude/skills/review-wiremock-mappings/SKILL.mdgit clone --depth 1 https://github.com/smartsheet/smartsheet-sdk-testsWrote 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/smartsheet/smartsheet-sdk-tests/review-wiremock-mappings)<a href="https://agentmods.dev/skills/smartsheet/smartsheet-sdk-tests/review-wiremock-mappings"><img src="https://agentmods.dev/badge/skills/smartsheet/smartsheet-sdk-tests/review-wiremock-mappings/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/smartsheet/smartsheet-sdk-tests/review-wiremock-mappings"><img src="https://agentmods.dev/badge/skills/smartsheet/smartsheet-sdk-tests/review-wiremock-mappings.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.00045 | $0.03170 |
| Opus 5 | $0.00023 | $0.01585 |
| Sonnet 5 | $0.00009 | $0.00634 |
| Haiku 4.5 | $0.00005 | $0.00317 |
Grade A, and why
review-wiremock-mappings 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 11d 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 — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewing WireMock Mappings for Smartsheet SDK
Overview
Systematically review WireMock mapping files for Smartsheet API endpoints to ensure they match OpenAPI specifications, exclude deprecated endpoints, and follow project conventions.
Core principle: Never approve mappings based on "looks reasonable". Always verify against OpenAPI spec and checklist.
When to Use
Use this skill when:
- Reviewing pull requests with WireMock mappings
- Verifying mappings before merge
- Code review of colleague's mapping submissions
- Quality checking existing mappings
- User asks "can you review these mappings"
Do NOT use for:
- Creating new mappings (use
create-wiremock-mappingsskill) - Non-Smartsheet API mocking
- Reviewing non-mapping code
Required Context
You need:
- Endpoint group being reviewed (e.g., "workspaces", "users")
- Location of mapping files (e.g.,
mappings/workspaces/) - OpenAPI specification source:
- Remote:
https://developers.smartsheet.com/_spec/api/smartsheet/openapi.json - Local: User-provided file path
- Remote:
References:
- CONTRIBUTING.md - Project conventions
- Creation checklist - Verification criteria
Review Workflow
digraph review_workflow {
"Start review" [shape=doublecircle];
"Identify endpoint group" [shape=box];
"Verify OpenAPI spec source" [shape=box];
"Check deprecated endpoints" [shape=box];
"Has mappings for deprecated?" [shape=diamond];
"BLOCK - deprecated included" [shape=box, style=filled, fillcolor=red];
"Verify all endpoints covered" [shape=box];
"Missing endpoints?" [shape=diamond];
"FLAG - incomplete coverage" [shape=box, style=filled, fillcolor=yellow];
"Verify schemas match spec" [shape=box];
"Schema mismatch?" [shape=diamond];
"BLOCK - schema incorrect" [shape=box, style=filled, fillcolor=red];
"Check project conventions" [shape=box];
"Conventions violated?" [shape=diamond];
"BLOCK - fix conventions" [shape=box, style=filled, fillcolor=red];
"Verify checklist items" [shape=box];
"All items pass?" [shape=diamond];
"APPROVE" [shape=doublecircle, style=filled, fillcolor=green];
"REQUEST CHANGES" [shape=doublecircle, style=filled, fillcolor=orange];
"Start review" -> "Identify endpoint group";
"Identify endpoint group" -> "Verify OpenAPI spec source";
"Verify OpenAPI spec source" -> "Check deprecated endpoints";
"Check deprecated endpoints" -> "Has mappings for deprecated?";
"Has mappings for deprecated?" -> "BLOCK - deprecated included" [label="yes"];
"Has mappings for deprecated?" -> "Verify all endpoints covered" [label="no"];
"BLOCK - deprecated included" -> "REQUEST CHANGES";
"Verify all endpoints covered" -> "Missing endpoints?";
"Missing endpoints?" -> "FLAG - incomplete coverage" [label="yes"];
"Missing endpoints?" -> "Verify schemas match spec" [label="no"];
"FLAG - incomplete coverage" -> "Verify schemas match spec";
"Verify schemas match spec" -> "Schema mismatch?";
"Schema mismatch?" -> "BLOCK - schema incorrect" [label="yes"];
"Schema mismatch?" -> "Check project conventions" [label="no"];
"BLOCK - schema incorrect" -> "REQUEST CHANGES";
"Check project conventions" -> "Conventions violated?";
"Conventions violated?" -> "BLOCK - fix conventions" [label="yes"];
"Conventions violated?" -> "Verify checklist items" [label="no"];
"BLOCK - fix conventions" -> "REQUEST CHANGES";
"Verify checklist items" -> "All items pass?";
"All items pass?" -> "APPROVE" [label="yes"];
"All items pass?" -> "REQUEST CHANGES" [label="no"];
}
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.
- 11d ago First seen · 354 lines · 45 tokens per session scan A 699e34910316
review-wiremock-mappings is a skill published in the GitHub repository smartsheet/smartsheet-sdk-tests (2 stars, last pushed 22d ago), licensed Apache-2.0. It adds 45 tokens to every session and 3,170 once invoked, about $0.0002 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
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.