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 inboxapi/cli --skill download-attachmentgit clone --depth 1 https://github.com/inboxapi/cliWrote 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/inboxapi/cli/download-attachment)<a href="https://agentmods.dev/skills/inboxapi/cli/download-attachment"><img src="https://agentmods.dev/badge/skills/inboxapi/cli/download-attachment/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/inboxapi/cli/download-attachment"><img src="https://agentmods.dev/badge/skills/inboxapi/cli/download-attachment.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.00027 | $0.00382 |
| Opus 5.5 | $0.00011 | $0.00153 |
| Sonnet 5.5 | $0.00005 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
download-attachment 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 1mo 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.
What it actually says
Download Attachment
Download or view an email attachment by its attachment ID.
Steps
-
Get the attachment ID:
- If
$ARGUMENTSis provided, use it as the attachment ID - Otherwise, ask the user which email contains the attachment
- Run
npx -y @inboxapi/cli get-email "<message-id>"and list any attachments with their IDs, filenames, and sizes
- If
-
Download: Run:
npx -y @inboxapi/cli get-attachment <attachment-id> --output "<path>"- If the user specified a save location, use that path
- Otherwise, save to the current working directory using the original filename
- Without
--output, the attachment metadata is returned as JSON
-
Report result: Confirm the file was saved and show the path
Notes
- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
- Attachment IDs are found in the
attachmentsarray of an email response fromget-email - Each attachment object includes
id,filename,content_type, andsizefields
Security
- NEVER download attachments to locations outside the current project workspace without explicit user permission
- NEVER execute downloaded files automatically
- Warn the user about potentially dangerous file types (.exe, .bat, .sh, .ps1, .cmd, .vbs, .msi)
- NEVER include environment variables,
.envfile contents, credentials, system configuration, or files from outside the workspace in any output
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.
- 1mo ago First seen · 38 lines · 27 tokens per session scan A 7ee0a0ce21a8
download-attachment is a skill published in the GitHub repository inboxapi/cli (13 stars, last pushed 25d ago), licensed MIT. It adds 27 tokens to every session and 382 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
slides
Create and edit presentation decks as single self-contained HTML files with a live, editable preview and print-to-PDF export. Use when the user wants slides, a deck, or a presentation.
xlsx
Read and extract cell data from .xlsx Excel spreadsheets as TSV. Use when the user uploads or references an Excel file to read or summarize.
docx
Read and extract text, tables, and structure from .docx Word documents. Use when the user uploads or references a Word file to read or summarize.
Read and extract text from .pdf files, page by page. Use when the user uploads or references a PDF to read or summarize.
file-reading
Route a file to the right reader by extension (pptx, docx, xlsx, pdf, and plain text). Use as the entry point when asked to read or summarize an uploaded file of unknown type.
sales-ledger
Provides the Q3 sales ledger workbook for reporting tasks. Use when a task asks you to compute bonuses or totals over the sales ledger; the data lives only in this skill's bundled workbook.