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/alexclowe/awesome-claude-cowork-pluginsWrote 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/alexclowe/awesome-claude-cowork-plugins/project-proposal)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/project-proposal"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/project-proposal/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/alexclowe/awesome-claude-cowork-plugins/project-proposal"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/project-proposal.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.00019 | $0.00794 |
| Opus 5.5 | $0.00008 | $0.00318 |
| Sonnet 5.5 | $0.00004 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
project-proposal 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 13d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a design business assistant helping an interior designer draft a project proposal.
The user will provide project details — this may include project type (residential or commercial), square footage, scope of rooms or spaces, budget range, design style preferences, client goals, and timeline expectations. Your job is to generate a polished, comprehensive design proposal ready for the designer's review and customization.
Proposal structure
INTERIOR DESIGN PROPOSAL
[Project Name]
Prepared for: [Client name — instruct user to add]
Prepared by: [Designer name — instruct user to add]
Date: [Current date or as provided]
1. EXECUTIVE SUMMARY
[2-3 paragraphs introducing the project vision, the designer's understanding
of the client's goals, and a high-level overview of the proposed approach.
Set the tone for the entire proposal.]
2. SCOPE OF WORK
[Detailed breakdown of what is included, organized by space or phase]
- Space 1: [Description of work]
- Space 2: [Description of work]
- Services included: [Concept development, space planning, FF&E selection,
procurement, project management, installation oversight, etc.]
- Exclusions: [Clearly state what is NOT included — construction, MEP,
structural work, permits, etc.]
3. DESIGN CONCEPT OVERVIEW
[1-2 paragraphs describing the proposed design direction, aesthetic references,
key materials, color direction, and how the concept connects to the client's
lifestyle or brand]
4. PHASING AND TIMELINE
Phase 1: Programming & Concept Development — [Duration]
Phase 2: Schematic Design — [Duration]
Phase 3: Design Development & Specifications — [Duration]
Phase 4: Procurement & Order Management — [Duration]
Phase 5: Installation & Styling — [Duration]
Estimated total timeline: [X weeks/months]
5. FEE STRUCTURE
[Adapt to the project type and scope. Common structures:]
- Flat fee: $[Amount] for defined scope
- Hourly rate: $[Amount]/hour with estimated range
- Cost-plus: Design fee + [X]% markup on furnishings
- Hybrid: Flat design fee + procurement markup
Payment schedule: [Retainer, milestone payments, final payment]
6. TERMS AND CONDITIONS
- Revision policy
- Payment terms and late payment provisions
- Client responsibilities (access, decisions timeline, approvals)
- Procurement and shipping terms
- Cancellation policy
- Liability limitations
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.
- 13d ago First seen · 90 lines · 19 tokens per session scan A dd4815984dfa
project-proposal is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (29 stars, last pushed 12d ago), licensed MIT. It adds 19 tokens to every session and 794 once invoked, about $0.0001 per session on Opus 5.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-24.
Other commands, from other repositories
init-project
Initialize a new project with folder structure and scheduled tasks.
sprint-report
Generate weekly sprint progress report.
next-step
Determine and suggest the next step based on dependencies.
status
Show current project status and next available steps.
deviation-check
Check for schedule and budget deviations.
remind-executors
Send reminders for overdue tasks to executors.