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/Amey-Thakur/AI-SKILLSWrote 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/amey-thakur/ai-skills/request-email)<a href="https://agentmods.dev/commands/amey-thakur/ai-skills/request-email"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/request-email/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/commands/amey-thakur/ai-skills/request-email"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/request-email.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.00383 |
| Opus 5 | $0.00014 | $0.00192 |
| Sonnet 5 | $0.00005 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
request-email 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 6d 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
You were invoked as a slash command. The user's input:
$ARGUMENTS
Use that input to fill this prompt's variables (take the main content, topic, or task from it; ask only if a required value is missing and not supplied), then follow the prompt exactly.
Write an email requesting: {request}
Context: {context}
Make it easy to say yes:
- State the ask clearly and reasonably early, so the reader knows exactly what you need. Do not bury it under paragraphs of preamble (see the bottom-line approach): the reader should not have to hunt for what you want.
- Give the context they need to decide: why you are asking, why them, and enough detail to act without a follow-up round.
- Make the request specific and bounded: exactly what, by when, in what form. A vague ask gets a vague or delayed response; a precise one is easy to fulfill.
- Lower the effort for them: attach what they need, offer to make it easier, suggest a small first step. The less work your request creates, the more likely the yes.
- Be courteous and appreciative without groveling, and give them a graceful way to decline if the ask is a real favor.
Rules: clear, specific, and considerate of their time. Match the tone to the relationship (more formal for a stranger or senior person, warmer for a colleague). Do not over-apologize for asking or pile on flattery; a respectful, direct request lands best. Include a fitting subject line. Mark anything I have not provided as a placeholder.
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.
- 6d ago First seen · 40 lines · 27 tokens per session scan A 3d9ca8b98c76
request-email is a command published in the GitHub repository Amey-Thakur/AI-SKILLS (7 stars, last pushed 7d ago), licensed MIT. It adds 27 tokens to every session and 383 once invoked, about $0.0001 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-09-06.
Other commands, from other repositories
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.