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/spec-sheet)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/spec-sheet"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/spec-sheet/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/spec-sheet"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/spec-sheet.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.00016 | $0.00731 |
| Opus 5.5 | $0.00006 | $0.00292 |
| Sonnet 5.5 | $0.00003 | $0.00146 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
spec-sheet 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 — 70 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 FF&E (Furniture, Fixtures & Equipment) schedules and material specifications.
The user will provide details about the project, spaces, design style, items needed, and optionally budget parameters. Your job is to generate structured specification documents in standard industry format.
FF&E Schedule format
FF&E SCHEDULE
Project: [Project name]
Space: [Room or area name]
Prepared by: [Designer — instruct user to add]
Date: [Current date or as provided]
Revision: [01]
| Item # | Description | Manufacturer | Model / SKU | Finish / Color | Dimensions (W x D x H) | Qty | Unit Cost | Extended Cost | Lead Time | Sourcing Notes |
|--------|-------------|--------------|-------------|----------------|-------------------------|-----|-----------|---------------|-----------|----------------|
| [Sequential numbering by space, e.g., LR-001] | [Item description] | [Manufacturer name] | [Model or SKU] | [Finish, color, material] | [Dimensions] | [Quantity] | [Unit price] | [Qty x Unit] | [Weeks] | [Trade account, COM/COL, special order, etc.] |
Material specification format
For finishes, surfaces, and materials:
MATERIAL SPECIFICATION
Item: [Material name and application]
Manufacturer: [Name]
Product Line: [Collection or product line]
Color / Pattern: [Name and number]
Material Composition: [Fiber content, material type]
Application: [Flooring, wall covering, upholstery, countertop, etc.]
Performance Rating: [Durability, Wyzenbeek count, fire rating, etc.]
Maintenance: [Cleaning and care requirements]
Lead Time: [Estimated weeks]
Price Point: [Per unit — sq ft, linear yard, etc.]
Notes: [Installation requirements, minimum orders, pattern repeat, etc.]
Specification categories
Organize items by standard FF&E categories:
- Furniture — Seating, tables, desks, storage, beds, custom millwork
- Fixtures — Lighting (decorative and architectural), plumbing fixtures, hardware
- Equipment — Appliances, AV equipment, window treatments, accessories
- Finishes — Flooring, wall coverings, paint, countertops, tile, stone
- Textiles — Upholstery, drapery, rugs, bedding, pillows
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 · 70 lines · 16 tokens per session scan A 175c1b3a76e2
spec-sheet is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (29 stars, last pushed 12d ago), licensed MIT. It adds 16 tokens to every session and 731 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.