flora-mcp-skills: Skill for Claude Code

.agents/skills/flora-run-technique/SKILL.md

flora-run-technique is a skill for Claude Code from florafauna-ai/flora-mcp-skills. It costs 108 tokens per session (720 once invoked), scanned A, original, MIT.

A workflow runner for FLORA, a service that provides saved image-processing workflows. Each technique combines fixed steps, prompts, and models for tasks such as changing backgrounds, relighting, upscaling, or turning sketches into rendered images.

In plain words
What is it for?
Use it to run a named FLORA technique on an existing image, such as swapping the background, changing the lighting, increasing resolution, changing the model, or creating a render from a sketch.
Why use it?
It helps you find the right saved workflow, provide its required image inputs, and avoid running a mismatched or incomplete process. It also checks the workspace and cost before a run.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents).

This is florafauna-ai/flora-mcp-skills's own configuration. It tells Claude Code how to work on flora-mcp-skills itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything flora-mcp-skills configures →

Part of the flora-mcp-skills plugin — 15 skills shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to florafauna-ai/flora-mcp-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/florafauna-ai/flora-mcp-skills/main/.agents/skills/flora-run-technique/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/florafauna-ai/flora-mcp-skills

Made for: Claude Code.

Or install flora-mcp-skills, the plugin that ships this one along with the rest of its 15 skills.

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 flora-run-technique

README.md
[![agentmods](https://agentmods.dev/badge/skills/florafauna-ai/flora-mcp-skills/flora-run-technique/github.svg)](https://agentmods.dev/skills/florafauna-ai/flora-mcp-skills/flora-run-technique)
Your own site
<a href="https://agentmods.dev/skills/florafauna-ai/flora-mcp-skills/flora-run-technique"><img src="https://agentmods.dev/badge/skills/florafauna-ai/flora-mcp-skills/flora-run-technique/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 flora-run-technique

Your own site · 80×15
<a href="https://agentmods.dev/skills/florafauna-ai/flora-mcp-skills/flora-run-technique"><img src="https://agentmods.dev/badge/skills/florafauna-ai/flora-mcp-skills/flora-run-technique.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 108 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 720 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.00108 $0.00720
Opus 5 $0.00054 $0.00360
Sonnet 5 $0.00022 $0.00144
Haiku 4.5 $0.00011 $0.00072

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

Security

Grade A, and why

flora-run-technique 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/skills/flora-run-technique/SKILL.md · 58 lines

How it starts

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

Run a FLORA technique

A technique is a saved workflow that chains several models. It is the thing FLORA does that a single image model cannot: the steps, prompts, and model choices are fixed by whoever authored it, so the same technique gives the same treatment every time.

Input: the user's intent, plus any source image. Output: the technique's output URLs, the charged cost, and the project the run landed in.

Steps

  1. Resolve the workspace. Call flora_list_workspaces. If there is more than one, ask which to bill before spending anything.

  2. Find the technique. Call flora_list_techniques and match on the user's intent. It returns run_cost and a summary of inputs for each. If nothing fits, say so and offer flora_generate instead — do not force an unrelated technique.

  3. Get the exact input ids. Call flora_get_technique. Its declared input ids are the keys flora_run_technique expects. Never guess them from the name.

  4. Get each image input to an HTTPS URL (see Image inputs below).

  5. Run it. Call flora_run_technique with workspace_id, technique_id, and an inputs object keyed by those ids. Omit optional text inputs entirely when the user gave no direction — an empty string is rejected, not treated as absent.

  6. Poll and report. Poll flora_get_run until status is completed or failed. Report the output URL, the charged cost, and a link to the project.

Image inputs

FLORA fetches images server-side from an HTTPS URL. Files the user attaches in ChatGPT already have one — they are hosted on files.openai.com or cdn.openai.com, both allowlisted. Pass that URL straight to flora_create_asset as source, or into the technique input directly.

Never base64-encode a file or try to upload bytes. If the image genuinely has no URL, say that this environment cannot upload it and point the user at their FLORA project to add it there.

Rules

  • State the cost before running. run_cost comes back from flora_list_techniques. Techniques range from free to several dollars per run.
  • You cannot see the output. Runs return URLs, not pixels. Describe what was produced from the technique and the inputs; never claim to have looked at it.
  • On input_validation_error, re-read flora_get_technique, rebuild inputs from what it returns, and retry once. Do not retry other failures — retries bill.
  • On insufficient credits, surface the message and stop.

Read the full file on GitHub · 58 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 · 58 lines · 108 tokens per session scan A e18230bbae2c

Subscribe to this mod's changes

flora-run-technique is a skill published in the GitHub repository florafauna-ai/flora-mcp-skills (8 stars, last pushed today), licensed MIT. It adds 108 tokens to every session and 720 once invoked, about $0.0005 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens