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 nota-america/forgecat-agent-profiles --skill draft-responsegit clone --depth 1 https://github.com/nota-america/forgecat-agent-profilesWrote 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/nota-america/forgecat-agent-profiles/draft-response)<a href="https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/draft-response"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/draft-response/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/nota-america/forgecat-agent-profiles/draft-response"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/draft-response.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.00053 | $0.03242 |
| Opus 5 | $0.00026 | $0.01621 |
| Sonnet 5 | $0.00011 | $0.00648 |
| Haiku 4.5 | $0.00005 | $0.00324 |
Grade A, and why
draft-response 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 8d 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.
This is a copy
100% identical to draft-response — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 422 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/draft-response
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md (
.forgecat/profiles/@forgecat/anthropics_knowledge-work-plugins_customer-support/CONNECTORS.md).
Draft a professional, customer-facing response tailored to the situation, customer relationship, and communication context.
Usage
/draft-response <context about the customer question, issue, or request>
Examples:
/draft-response Acme Corp is asking when the new dashboard feature will ship/draft-response Customer escalation — their integration has been down for 2 days/draft-response Responding to a feature request we won't be building/draft-response Customer hit a billing error and wants a resolution ASAP
Workflow
1. Understand the Context
Parse the user's input to determine:
- Customer: Who is the communication for? Look up account context if available.
- Situation type: Question, issue, escalation, announcement, negotiation, bad news, good news, follow-up
- Urgency: Is this time-sensitive? How long has the customer been waiting?
- Channel: Email, support ticket, chat, or other (adjust formality accordingly)
- Relationship stage: New customer, established, frustrated/escalated
- Stakeholder level: End user, manager, executive, technical, business
2. Research Context
Gather relevant background from available sources:
~~email:
- Previous correspondence with this customer on this topic
- Any commitments or timelines previously shared
- Tone and style of the existing thread
~~chat:
- Internal discussions about this customer or topic
- Any guidance from product, engineering, or leadership
- Similar situations and how they were handled
~~CRM (if connected):
- Account details and plan level
- Contact information and key stakeholders
- Previous escalations or sensitive issues
~~support platform (if connected):
- Related tickets and their resolution
- Known issues or workarounds
- SLA status and response time commitments
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.
- 8d ago First seen · 422 lines · 53 tokens per session scan A 7bf4a3fbc380
draft-response is a skill published in the GitHub repository nota-america/forgecat-agent-profiles (66 stars, last pushed yesterday), licensed Apache-2.0. It adds 53 tokens to every session and 3,242 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to draft-response, differing in 9 lines, and is treated as a copy.
Other skills, from other repositories
aoa-agents-skills
Form, transfer, continue, or receive an independent AoA responsibility with a role-bearing actor. Use when an obligation needs its own holder, mandate, or continuity across incarnations. Ordinary tasks and native Codex helpers do not need this skill.
aoa-session-progression-lift
Turn closed, reviewed session evidence into a bounded multi-axis progression candidate with baseline and attribution limits for aoa-agents review. Do not use on live impressions, without a baseline, to assign one universal score, mutate a role, grant authority, or set routing policy.
aoa-summon
Decide or execute a complete summon-request-v4 for an independent external AoA actor and return a validated summon-result-v4. Use as the aoa-agents-skills execution leaf or to inspect an explicit legacy summon packet. Ordinary native Codex helpers do not use this leaf.
abs
The CLI of the AI Agent Economy. The first CLI social network and marketplace for AI agents. Humans are in the loop for claiming agents (GitHub OAuth), approving purchases, and completing seller onboarding.
agent-skills-evaluator
AI Agent Management Clis Hint and Completion Skill.
agent-cli-hint-completion
AI Agent Management Clis Hint and Completion Skill.