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 commands/eric861129/skills_all-in-one/deapi-setupgit clone --depth 1 https://github.com/eric861129/SKILLS_All-in-oneWrote 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/commands/eric861129/skills_all-in-one/deapi-setup)<a href="https://agentmods.dev/commands/eric861129/skills_all-in-one/deapi-setup"><img src="https://agentmods.dev/badge/commands/eric861129/skills_all-in-one/deapi-setup.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.00023 | $0.00935 |
| Opus 5 | $0.00012 | $0.00467 |
| Sonnet 5 | $0.00005 | $0.00187 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
deapi-setup scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://api.deapi.ai/api/v1/client/request-status/{request_id}" \ Copies of this mod
1 near-identical copy found in the catalogue:
- deapi-setup — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Result Delivery Setup
Configure how your application receives job results.
Step 1: Determine context
Ask user about their use case:
| Context | Recommended method |
|---|---|
| CLI tool, local script | Polling (default) |
| Backend server, serverless | Webhooks |
| Real-time UI, SPA | WebSockets |
Step 2: Configure based on method
Polling (default)
No configuration needed. Use /request-status/{id} endpoint.
Already built into all deAPI commands.
curl -s "https://api.deapi.ai/api/v1/client/request-status/{request_id}" \
-H "Authorization: Bearer $DEAPI_API_KEY"
Poll every 10 seconds until status = "done".
Webhooks
Add webhook_url to any request:
{
"prompt": "...",
"webhook_url": "https://your-server.com/webhooks/deapi"
}
Events received:
job.completed- containsresult_urljob.failed- containserror_code
Security: Verify signature in X-DeAPI-Signature header (HMAC-SHA256).
Full docs: https://docs.deapi.ai/execution-modes-and-integrations/webhooks
WebSockets
Connect via Pusher protocol for real-time updates:
| Setting | Value |
|---|---|
| Host | soketi.deapi.ai:443 |
| Channel | private-client.{client_id} |
| Event | request.status.updated |
Includes live preview images during generation.
Full docs: https://docs.deapi.ai/execution-modes-and-integrations/websockets
Step 3: Generate boilerplate
Based on user's choice, generate starter code for their stack.
Webhook handler (Node.js/Express):
app.post('/webhooks/deapi', (req, res) => {
const signature = req.headers['x-deapi-signature'];
// Verify signature with your webhook secret
const { event, request_id, result_url, error } = req.body;
if (event === 'job.completed') {
// Process result from result_url
} else if (event === 'job.failed') {
// Handle error
}
res.status(200).send('OK');
});
Webhook handler (Python/FastAPI):
from fastapi import FastAPI, Request, Header
app = FastAPI()
@app.post("/webhooks/deapi")
async def deapi_webhook(
request: Request,
x_deapi_signature: str = Header(None)
):
# Verify signature with your webhook secret
body = await request.json()
if body["event"] == "job.completed":
result_url = body["result_url"]
# Process result
elif body["event"] == "job.failed":
error = body["error"]
# Handle error
return {"status": "ok"}
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 · 151 lines · 23 tokens per session scan A 923459ded2db
deapi-setup is a command published in the GitHub repository eric861129/SKILLS_All-in-one (52 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 935 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
show-off
Generate impressive multi-section HTML presentations with parallax, theme toggle, bilingual VI/EN — then auto-capture as 16:9, 9:16, 1:1 social-ready images.
coding-level
Set Claude's coding explanation level for this session/project (-1=Default → 5=God Mode).
plan
Plan a feature or system with auto-detected complexity. Modes (pick one): --fast (quick plan → cook), --hard (research + red-team + validate). Composable flag (any mode): --tdd (tests-first per phase). Every phase gets Design Constraints and Quality/Testing State for the mandatory cook quality gate. Always starts with…
test
Standalone testing skill. Default analyzes changed scope and runs relevant tests; --unit/--integration/--e2e/--all scope by type; --verify reruns prior failures; --all-phases sweeps every completed phase. --tdd --prepare /--tdd --verify bracket ck:cook for red-green TDD. Never edits production code; blocks until the…
brainstorm
Explore and debate solutions before writing code — scout codebase, ask clarifying questions, research options, and produce a structured decision report. Ends with → /ck:plan (implement) or /ck:journal (archive). No code is written.
review
/review — Request code review.