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.
git 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/upscale)<a href="https://agentmods.dev/commands/eric861129/skills_all-in-one/upscale"><img src="https://agentmods.dev/badge/commands/eric861129/skills_all-in-one/upscale.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.00011 | $0.00627 |
| Opus 5 | $0.00005 | $0.00313 |
| Sonnet 5 | $0.00002 | $0.00125 |
| Haiku 4.5 | $0.00001 | $0.00063 |
Grade A, and why
upscale 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 5d 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 -X POST "https://api.deapi.ai/api/v1/client/img-upscale" \ Copies of this mod
1 near-identical copy found in the catalogue:
- upscale — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Image Upscaling via deAPI
Upscale image: $ARGUMENTS
Step 1: Parse arguments
Extract from $ARGUMENTS:
image: Image file path or URL (required)--scale: Upscale factor -2(2x, default) or4(4x)
Model options (based on scale):
| Scale | Model | Result |
|---|---|---|
2 |
RealESRGAN_x2 |
2x resolution (e.g., 512→1024) |
4 |
RealESRGAN_x4 |
4x resolution (e.g., 512→2048) |
Step 2: Send request
Note: This endpoint requires multipart/form-data with file upload.
curl -s -X POST "https://api.deapi.ai/api/v1/client/img-upscale" \
-H "Authorization: Bearer $DEAPI_API_KEY" \
-F "image=@{local_file_path}" \
-F "model=RealESRGAN_x4"
If user provides a URL, first download the image:
curl -s -o /tmp/upscale_image.png "{image_url}"
Then use /tmp/upscale_image.png as the file path.
Step 3: Poll status (feedback loop)
Extract request_id from response, then poll every 10 seconds:
curl -s "https://api.deapi.ai/api/v1/client/request-status/{request_id}" \
-H "Authorization: Bearer $DEAPI_API_KEY"
Status handling:
processing→ wait 10s, poll againdone→ proceed to Step 4failed→ report error message to user, STOP
Step 4: Fetch and present result
When status = "done":
- Get upscaled image URL from
result_url - Show original vs new dimensions
- Provide download link to user
Step 5: Offer follow-up
Ask user:
- "Would you like to upscale further (if 2x was used)?"
- "Should I remove the background from this image?"
- "Would you like to process another image?"
Error handling
| Error | Action |
|---|---|
| 401 Unauthorized | Check if $DEAPI_API_KEY is set correctly |
| 429 Rate Limited | Wait 60s and retry |
| 500 Server Error | Wait 30s and retry once |
| Invalid URL | Ask user to verify the image URL |
| Image too large | 4x upscaling has size limits; suggest 2x instead |
| Unsupported format | Convert to PNG/JPG first |
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.
- 5d ago First seen · 78 lines · 11 tokens per session scan A 0f8a001b0299
upscale is a command published in the GitHub repository eric861129/SKILLS_All-in-one (52 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 627 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.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.