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 agentmods add skills/vladkesler/initrunner/api-contract-testingnpx skills add vladkesler/initrunner --skill api-contract-testinggit clone --depth 1 https://github.com/vladkesler/initrunnerWhat 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 | $0.00030 | $0.01023 |
| Opus 5 | $0.00015 | $0.00511 |
| Sonnet 5 | $0.00006 | $0.00205 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade D, and why
api-contract-testing scanned grade D with 3 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 2d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -s -X POST -H 'Content-Type: application/json' -d '{"key":"value"}' http://host:port/path Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -s http://host:port/path | python -c " Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
bins: [curl] How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API contract testing skill using curl and inline validation scripts.
When to activate
Use this skill when the project has API endpoints: an OpenAPI/Swagger spec, a routes directory, an Express/FastAPI/Flask/Rails app entrypoint, or existing API test files. Also activate when integration tests reference HTTP endpoints or when a new endpoint has been added.
Probing commands
Status code extraction
curl -s -w '\n%{http_code}' http://host:port/path
The last line of output is the HTTP status code. Capture it separately from the response body.
Response body
curl -s http://host:port/path
Use -s (silent) to suppress progress bars.
Timing
curl -s -o /dev/null -w '%{time_total}' http://host:port/path
Record total request time for baseline comparison.
Sending payloads
curl -s -X POST -H 'Content-Type: application/json' -d '{"key":"value"}' http://host:port/path
Always set the Content-Type header explicitly when sending a body.
Status validation
- 2xx -- expected for healthy endpoints and valid requests
- 4xx -- expected for bad input, missing auth, or not-found resources; verify that the status matches the specific error condition (400 for malformed input, 401 for missing auth, 403 for forbidden, 404 for unknown resource, 422 for validation failure)
- 5xx -- indicates a bug or unhandled exception in the service; always flag these as failures unless explicitly expected
Response body checks
Use inline scripts to validate JSON structure:
curl -s http://host:port/path | python -c "
import sys, json
data = json.load(sys.stdin)
assert 'id' in data, 'missing id field'
assert isinstance(data['id'], int), 'id must be integer'
"
Or with Node.js if Python is unavailable:
curl -s http://host:port/path | node -e "
const data = JSON.parse(require('fs').readFileSync(0,'utf8'));
if (!data.id) { console.error('missing id'); process.exit(1); }
"
Check:
- Required fields exist and are non-null
- Field types match expectations (string, integer, array, object)
- Array responses have expected length or are non-empty
- Nested objects have required sub-fields
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.
- 2d ago First seen · 147 lines · 30 tokens per session scan D 8c711070d8be
api-contract-testing is a skill published in the GitHub repository vladkesler/initrunner (41 stars, last pushed 4d ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,023 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it D with 3 findings (sends data to an external url, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
Vizra ADK Evaluation Framework
Test and evaluate AI agents with automated evaluations, assertions, and LLM-as-a-Judge patterns.
Vizra ADK Tool Creation
Build custom tools for Vizra ADK agents - includes patterns for database, API, file, and email tools.
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
Vizra ADK Workflows
Orchestrate complex multi-agent workflows - sequential, parallel, conditional, and loop patterns.
Vizra ADK Agent Creation
Create AI agents with Vizra ADK - includes patterns for customer service, data analysis, and content generation agents.
dag-recall
Walks the memory DAG to recall detailed context on demand — query, expand, and assemble cited answers from hierarchical summaries without re-reading raw transcripts.