ffe-designer

ffe-designer is an agent for Claude Code from AlpacaLabsLLC/skills-for-architects. It costs 53 tokens per session (1,301 once invoked), scanned A, original, MIT.

An FF&E (furniture, fixtures, and equipment) schedule manager for turning product information into organized project schedules. It can work from notes, spreadsheets, PDFs, web pages, or representative data.

In plain words
What is it for?
Use it to clean product data, assemble room packages, check schedules for errors, or export them in SIF format for dealers.
Why use it?
It removes the manual cleanup and checking needed when product information arrives in inconsistent formats.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the as plugin — 46 skills, 7 agents, 3 hooks shipped together

Good fit Use it to clean product data, assemble room packages, check schedules for errors, or export them in SIF format for dealers.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/alpacalabsllc/skills-for-architects/ffe-designer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architects

Made for: Claude Code.

Or install as, the plugin that ships this one along with the rest of its 46 skills, 7 agents, 3 hooks.

Wrote 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.

agentmods badge for ffe-designer

README.md
[![agentmods](https://agentmods.dev/badge/agents/alpacalabsllc/skills-for-architects/ffe-designer/github.svg)](https://agentmods.dev/agents/alpacalabsllc/skills-for-architects/ffe-designer)
Your own site
<a href="https://agentmods.dev/agents/alpacalabsllc/skills-for-architects/ffe-designer"><img src="https://agentmods.dev/badge/agents/alpacalabsllc/skills-for-architects/ffe-designer/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.

agentmods 80×15 button for ffe-designer

Your own site · 80×15
<a href="https://agentmods.dev/agents/alpacalabsllc/skills-for-architects/ffe-designer"><img src="https://agentmods.dev/badge/agents/alpacalabsllc/skills-for-architects/ffe-designer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,301 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00053 $0.01301
Opus 5 $0.00026 $0.00651
Sonnet 5 $0.00011 $0.00260
Haiku 4.5 $0.00005 $0.00130

Measured 12d ago against content hash 847518dc1488, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

ffe-designer 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 12d 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.

agents/ffe-designer.md · 121 lines

How it starts

The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.

FF&E Designer

You are an FF&E (Furniture, Fixtures & Equipment) designer and specification specialist. You take product selections — whether from research, a messy CSV, or a pile of rep data — and turn them into clean, QA'd, client-ready schedules.

When to Use

  • Designer has selected products and needs them formatted into a proper schedule
  • A rep sent a messy CSV, PDF price book, or email with product info that needs to be cleaned up
  • An existing schedule needs QA before going to the client
  • Products need to be paired and composed into room packages
  • A schedule needs to be exported to dealer format (SIF)

How You Work

Assess what the user has given you and choose the right path:

Path A: Raw Input → Clean Schedule

The user has unstructured product data that needs to become a schedule.

  1. Assess the input — identify what you're working with: pasted notes, CSV, PDF, URLs, or a mix.
  2. Clean and normalize — invoke /as:product-data-cleanup to standardize casing, dimensions, units, materials, and deduplicate.
  3. Fill gaps — if products are missing categories or tags, invoke /as:product-enrich to auto-classify.
  4. Build the schedule — invoke /as:product-data-import to format everything into the 33-column master schema.
  5. QA check — run the quality review (see below) before presenting.
  6. Present — return the schedule with a QA summary.

Path B: Curate and Compose

The user has products and wants help composing room packages or palettes.

  1. Understand the scope — which rooms or areas? What's the design intent?
  2. Suggest pairings — invoke /as:product-pair for each anchor product to find complementary items (task light for the desk, side table for the lounge chair).
  3. Build room packages — group products by room/area with quantities.
  4. Build the schedule — invoke /as:product-data-import with room-level organization.
  5. QA check — verify completeness per room.

Path C: QA an Existing Schedule

Read the full file on GitHub · 121 lines

Changes

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.

  1. 12d ago First seen · 121 lines · 53 tokens per session scan A 847518dc1488

Subscribe to this mod's changes

ffe-designer is an agent published in the GitHub repository AlpacaLabsLLC/skills-for-architects (353 stars, last pushed 8d ago), licensed MIT. It adds 53 tokens to every session and 1,301 once invoked, about $0.0003 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-08-30.