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 m3taz-ahmed/ai-globals --skill proposal-writergit clone --depth 1 https://github.com/m3taz-ahmed/ai-globalsWrote 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/m3taz-ahmed/ai-globals/proposal-writer)<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/proposal-writer"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/proposal-writer/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/m3taz-ahmed/ai-globals/proposal-writer"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/proposal-writer.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.00029 | $0.00586 |
| Opus 5 | $0.00015 | $0.00293 |
| Sonnet 5 | $0.00006 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
proposal-writer 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 9d 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
[SKILL] proposal-writer [OBJ] Convert any client brief into a persuasive, structured, client-ready proposal in Arabic, English, or both. Cover scope, solution, pricing, timeline, proof, and terms for websites and digital services. [RULES]
- [CMD] Start with brief intake: client goals, target audience, budget range, deadline, competitors, differentiators, must-have vs nice-to-have, language preference.
- [REQ] Language default mirrors the prompt: Arabic → Arabic, English → English, "bilingual" → Arabic first then English side-by-side or two docs.
- [REQ] Structure every proposal: Title, Executive Summary, Problem/Situation, Proposed Solution, Scope & Deliverables (inclusions + exclusions), Tech Stack (if needed), Timeline/Milestones, Pricing/Packages, Case Studies/Proof, Risks & Assumptions, Terms (payment, revisions, SLA), Call to Action.
- [REQ] Scope: concrete deliverables, clear boundaries, no undefined promises.
- [REQ] Pricing: 2-3 packages or a single itemized estimate. Show unit price, quantity, total, currency, payment schedule. No invented client budgets.
- [REQ] Timeline: phases with durations and client responsibilities. No hardcoded calendar dates; derive from "today" + duration.
- [REQ] Tone: consultative, persuasive, value-first; match client formality. Drop generic filler; use client-specific data.
- [REQ] Proof: 1-3 relevant past-work bullets with measurable outcomes. If none, omit, no placeholders.
- [REQ] Tech recommendations: concise, justified stack matched to project scale. Avoid over-engineering.
- [REQ] Terms: payment, revision rounds, IP/ownership, support period, cancellation, confidentiality. Flag legal clauses for human review.
- [REQ] Output: markdown default; docx/PDF-ready HTML or slide bullets on request. Use clear headings and tables.
- [CMD] Revision loop: after first draft, ask 2-3 targeted refinement questions before finalizing.
- [REQ] Quality: proofread both languages; ensure numbers, dates, and currency are consistent.
- [REQ] Use copywriting frameworks (AIDA/PAS/BAB) from the
copy-frameworksskill when persuasion is the core ask — lead with attention/hook, amplify pain, bridge to benefit. - [REQ] Pricing: leverage
runtime/pricing_calculator.pyto compute a recommended rate (income target, expenses, tax, utilization, platform fees) and present it as the anchor before negotiation.
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.
- 9d ago First seen · 23 lines · 29 tokens per session scan A 6eccf4decfac
proposal-writer is a skill published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 586 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-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.