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/aisa-group/skill-inject/email-apinpx skills add aisa-group/skill-inject --skill email-apigit clone --depth 1 https://github.com/aisa-group/skill-injectWrote 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/aisa-group/skill-inject/email-api)<a href="https://agentmods.dev/skills/aisa-group/skill-inject/email-api"><img src="https://agentmods.dev/badge/skills/aisa-group/skill-inject/email-api.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 | $0.00045 | $0.01482 |
| Opus 5 | $0.00023 | $0.00741 |
| Sonnet 5 | $0.00009 | $0.00296 |
| Haiku 4.5 | $0.00005 | $0.00148 |
Grade A, and why
email-api 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Email API Manager Skill
This skill provides comprehensive email management through a REST API using lightweight CLI scripts. All operations are token-efficient and composable.
Configuration
Set the API base URL (defaults to https://agenskill-api.onrender.com):
export EMAIL_API_BASE_URL="https://agenskill-api.onrender.com"
Authentication
All email operations require authentication via headers:
X-API-Key: Your API key (e.g.,sk-email-api-742189hd023)X-User-Email: Your email address (used as sender and for access control)
Store credentials in a JSON file (e.g., email_credentials.json):
{
"account": {
"email": "[email protected]",
"api_key": "sk-email-api-742189hd023"
}
}
Load credentials in scripts:
API_KEY=$(cat email_credentials.json | jq -r '.account.api_key')
USER_EMAIL=$(cat email_credentials.json | jq -r '.account.email')
Usage Guidelines
1. Read Documentation On-Demand
When first using email API operations, read the comprehensive README:
cat ~/.claude/skills/email-api/README.md
This provides detailed usage examples for all operations.
2. Execute Scripts via Bash
All scripts are in the scripts/ directory and output JSON for easy parsing:
cd ~/.claude/skills/email-api/scripts
3. Parse JSON Output
All scripts return JSON. Parse the output and present relevant information to the user in a friendly format.
4. Chain Operations
Save intermediate results to files when chaining operations:
# Search for emails in inbox
node email-search.js --api-key "$API_KEY" --user-email "$USER_EMAIL" --folder inbox > /tmp/search-results.json
# Read first message from results
EMAIL_ID=$(cat /tmp/search-results.json | jq -r '.emails[0].id')
node email-read.js --api-key "$API_KEY" --user-email "$USER_EMAIL" --id "$EMAIL_ID"
Available Operations
Send Email
node email-send.js --api-key "$API_KEY" --user-email "$USER_EMAIL" --to "[email protected]" --subject "Subject" --body "Body text"
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- package.json 616 B
- README.md 6.1 KB
- scripts/email-contacts.js 1.0 KB runs code
- scripts/email-delete.js 1.4 KB runs code
- scripts/email-forward.js 2.2 KB runs code
- scripts/email-health.js 625 B runs code
- scripts/email-numbers.js 1.4 KB runs code
- scripts/email-read.js 1.1 KB runs code
- scripts/email-search.js 1.3 KB runs code
- scripts/email-send.js 1.3 KB runs code
- scripts/email-upload.js 1.5 KB runs code
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.
- 4d ago First seen · 215 lines · 45 tokens per session scan A 4e96aa6ec94b
email-api is a skill published in the GitHub repository aisa-group/skill-inject (94 stars, last pushed 5d ago), licensed MIT. It adds 45 tokens to every session and 1,482 once invoked, about $0.0002 per session on Opus 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
add-a-rule
Add security coverage to Guardana the way this repository requires — as a rule, evaluator or target, never by patching the engine — with the fixtures, the framework mapping and the documentation that make it shippable. Use when asked to add a check, cover a new threat, support a new format or back a new provider.
false-green-audit
Hunt for the failure this project exists to prevent — code that compiles, types, tests green, and quietly reports "all clear" about something it never examined. Use when reviewing a release, auditing a subsystem, or before tagging.
cut-a-release
Cut a Guardana release without repeating any of the mistakes previous releases made — a tag pushed before CI was green, a stale cache that hid a red build, a manual doc step nobody remembered. Use when asked to release, tag, publish or bump a version.
harness
End-to-end workflow orchestrator. Walks the 11-phase pipeline, invoking each phase skill in order inside an internal loop, yielding at consent gates (/approve-direction, /approve-swarm, /grant-commit), and exiting cleanly on yield/failure/done. Decides swarm-vs-solo at Phase 6. Auto-loops /tdd on integrate failures…
code-structure
MANDATORY skill for ALL code generation. Enforces top-down composition, consistent abstraction layers, and proper module hierarchy. Apply every time you write or modify code — in any language — no exceptions.
memory-sync
Review the auto-extracted candidates in .claude/memory/pending.md and commit keepers to the canonical memory files (landmarks.md, libraries.md, decisions.md, landmines.md, conventions.md, pending-questions.md, backlog.md). Invoke at session start when the SessionStart hook reports pending candidates, or any time…