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/arise-ai-group/lead-management-plugin/proposal-assemblynpx skills add Arise-AI-Group/lead-management-plugin --skill proposal-assemblygit clone --depth 1 https://github.com/Arise-AI-Group/lead-management-pluginWrote 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/arise-ai-group/lead-management-plugin/proposal-assembly)<a href="https://agentmods.dev/skills/arise-ai-group/lead-management-plugin/proposal-assembly"><img src="https://agentmods.dev/badge/skills/arise-ai-group/lead-management-plugin/proposal-assembly.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.1 | $0.00000 | $0.01974 |
| Opus 5 | $0.00000 | $0.00987 |
| Sonnet 5 | $0.00000 | $0.00395 |
| Haiku 4.5 | $0.00000 | $0.00197 |
Grade A, and why
proposal-assembly 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.
How it starts
The opening of the file, as written. The whole thing — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proposal Assembly
Build professional proposals from discovery data — auto-populate templates, route for team review, and get from "interested" to "here's our proposal" fast.
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ PROPOSAL ASSEMBLY │
├─────────────────────────────────────────────────────────────────┤
│ STANDALONE (always works) │
│ ✓ You tell me: client, their needs, your services, pricing │
│ ✓ Generate structured proposal with all standard sections │
│ ✓ Personalized approach section referencing discovery data │
│ ✓ Pricing table with clear deliverables and timeline │
│ ✓ Output: ready-to-send proposal document │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + CRM: Pull client data, discovery notes, pain points auto │
│ + Chat: Route for team review with SLA tracking │
│ + Email: Send proposal directly to client │
│ + E-signature: Generate PDF and create signing envelope │
└─────────────────────────────────────────────────────────────────┘
Getting Started
Required:
- Client name and company
- What services you're proposing
- Pricing (or "help me figure out pricing")
Helpful if you have it:
- Discovery call notes or transcript summary
- Pain points they mentioned
- Their timeline and budget range
- Decision makers and their priorities
- Any specific requests or constraints they mentioned
If CRM is connected, I'll pull discovery notes and client data automatically.
Connectors (Optional)
| Connector | What It Adds |
|---|---|
| ~~CRM | Pull client data, discovery notes, pain points, prior proposals |
| ~~chat | Route proposal for team review with SLA reminders |
| Send completed proposal to client | |
| ~~e-signature | Generate PDF, create signing envelope, send for signature |
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 · 298 lines · 0 tokens per session scan A 9d076db583a2
proposal-assembly is a skill published in the GitHub repository Arise-AI-Group/lead-management-plugin (7 stars, last pushed 7mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,974 tokens. 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…