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 sairam0424/MindForge --skill rest-graphql-debuggit clone --depth 1 https://github.com/sairam0424/MindForgeWrote 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/sairam0424/mindforge/rest-graphql-debug)<a href="https://agentmods.dev/skills/sairam0424/mindforge/rest-graphql-debug"><img src="https://agentmods.dev/badge/skills/sairam0424/mindforge/rest-graphql-debug.svg" alt="Measured on agentmods" 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.00021 | $0.03940 |
| Opus 5 | $0.00010 | $0.01970 |
| Sonnet 5 | $0.00004 | $0.00788 |
| Haiku 4.5 | $0.00002 | $0.00394 |
Grade D, and why
rest-graphql-debug 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 3d 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.
resp = requests.post( "https://api.example.com/graphql", 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.
Bash('curl -s https://api.example.com/users | python3 -m json.tool') Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Drive REST and GraphQL diagnosis through tools — `Bash` for `curl`, `Bash` for Python `requests`, `WebFetch` for vendor docs. Isolate the failing layer before guessing at the fix. This is a copy
89% identical to rest-graphql-debug — 73 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 507 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Testing & Debugging
Drive REST and GraphQL diagnosis through tools — Bash for curl, Bash for Python requests, WebFetch for vendor docs. Isolate the failing layer before guessing at the fix.
When to Use
- API returns unexpected status or body
- Auth fails (401/403 after token refresh, OAuth, API key)
- Works in Postman but fails in code
- Webhook / callback integration debugging
- Building or reviewing API integration tests
- Rate limiting or pagination issues
Skip for UI rendering, DB query tuning, or DNS/firewall infra (escalate).
Core Principle
Isolate the layer, then fix. A 200 OK can hide broken data. A 500 can mask a one-character auth typo. Walk the chain in order; never skip a step.
1. Connectivity → can we reach the host at all?
1.5 Timeouts → connect-slow vs read-slow?
2. TLS/SSL → cert valid and trusted?
3. Auth → credentials correct and unexpired?
4. Request format → payload shape match server expectations?
5. Response parse → does our code accept what came back?
6. Semantics → does the data mean what we assume?
5-Minute Quickstart
REST via terminal
# Verbose request/response exchange
Bash('curl -v https://api.example.com/users/1')
# POST with JSON
Bash("""curl -X POST https://api.example.com/users \\
-H 'Content-Type: application/json' \\
-H "Authorization: Bearer $TOKEN" \\
-d '{"name":"test","email":"[email protected]"}'""")
# Headers only
Bash('curl -sI https://api.example.com/health')
# Pretty-print JSON
Bash('curl -s https://api.example.com/users | python3 -m json.tool')
GraphQL via terminal
Bash("""curl -X POST https://api.example.com/graphql \\
-H 'Content-Type: application/json' \\
-H "Authorization: Bearer $TOKEN" \\
-d '{"query":"{ user(id: 1) { name email } }"}'""")
GraphQL gotcha: servers often return HTTP 200 even when the query failed. Always inspect the errors field regardless of status code:
Bash('''
import os, requests
resp = requests.post(
"https://api.example.com/graphql",
json={"query": "{ user(id: 1) { name email } }"},
headers={"Authorization": f"Bearer {os.environ['TOKEN']}"},
timeout=10,
)
data = resp.json()
if data.get("errors"):
for err in data["errors"]:
print(f"GraphQL error: {err['message']} (path: {err.get('path')})")
print(data.get("data"))
''')
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.
- 3d ago First seen · 507 lines · 21 tokens per session scan D 95eb9381bff4
rest-graphql-debug is a skill published in the GitHub repository sairam0424/MindForge (0 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 3,940 once invoked, about $0.0001 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). It is 89% identical to rest-graphql-debug, differing in 73 lines, and is treated as a copy.
Other skills, from other repositories
error-handling-patterns
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
backend-implementation-review
Use when you need to review server-side implementation for correctness, maintainability, validation, and observability.
integration-boundary-review
Use when you need to review third-party service, webhook, queue, and cross-system integration boundaries.
python-error-handling
Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.
cao-provider
Create a new CLI agent provider for CAO (CLI Agent Orchestrator). Use this skill whenever the user wants to add support for a new CLI-based AI agent (e.g., a new coding assistant CLI), integrate a new provider, or scaffold a provider implementation. Also use when the user asks about the provider architecture, what…
ap-depth-prober
L4 terminal leaf - G3.5 DEPTH-LOCK. Independently derives the bug's deepest-cause function from the ISSUE TEXT alone, blind to the proposed fix layer; default-FAIL. Emits D1-D5. depth-miss REJECTs to G1.