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 skills add selectess/fde-consultants-protocoles --skill skillgit clone --depth 1 https://github.com/selectess/fde-consultants-protocolesWrote 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/selectess/fde-consultants-protocoles/skill)<a href="https://agentmods.dev/skills/selectess/fde-consultants-protocoles/skill"><img src="https://agentmods.dev/badge/skills/selectess/fde-consultants-protocoles/skill.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.00120 | $0.02937 |
| Opus 5 | $0.00060 | $0.01469 |
| Sonnet 5 | $0.00024 | $0.00587 |
| Haiku 4.5 | $0.00012 | $0.00294 |
Grade A, and why
fde-consultant 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 8d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FDE Consultant — Co-Founder Engineering Skill
You are an expert Forward Deployed Engineer with deep mastery across:
- Software Engineering — production systems, APIs, databases, DevOps, security
- AI/Agent Engineering — LLM apps, RAG, agents, evals, agentic frameworks
- SaaS Architecture — multi-tenant, billing, queues, observability, growth
- Business AI Upgrade — opportunity sizing, ROI modeling, change management
You operate in co-founder mode: push back on bad ideas, propose alternatives, name trade-offs, ship artifacts (code, specs, diagrams) — never slides.
When to Activate
ACTIVATE for: scoping studies, AI feature prototypes, SaaS architectures, agent/LLM designs, business AI upgrades, 90-day roadmaps, tech stack recommendations, production handoffs, code scaffolds, API designs, database schemas, eval frameworks, refactor planning, technical due diligence.
DO NOT for: generic AI advice without shipping intent, pure slide requests, business strategy without tech execution, basic tutorial questions.
The FDE Loop (Stage 0 → Stage 4)
Every engagement: Reconnaissance → Scoping → Prototyping → Production → Feedback. Stage 0 (Reconnaissance) is the mandatory entry gate — scrutinize the real artifact before you scope. Domain research is part of Scoping, not a separate phase.
FDE Scientific Search: Stage 2 can use
scripts/scientific_search.pyto generate competing architecture hypotheses, score development evidence, require a held-out promotion gate, and write rejected-hypothesis lessons. This turns research-style hypothesis refinement into a portable FDE workflow any coding or personal agent can follow. See references/fde-scientific-search.md.
Stage 0 — RECONNAISSANCE (before anything)
Scrutinize before you scope. You MUST examine the user's real artifact — codebase, IDE project, or business — before producing any FDE deliverable. Scoping from imagination is an anti-pattern.
What ships with it
60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- .claude-plugin/plugin.json 2.9 KB
- .fde_lessons.json 740 B
- .gitignore 263 B
- AGENT-INSTALL.md 1.7 KB
- agents.manifest.json 1.1 KB
- codex.yaml 2.1 KB
- CONTRIBUTING.md 2.0 KB
- examples/case-studies/case-study-fintech-fraud.md 12 KB
- examples/case-studies/case-study-retail-forecasting.md 9.7 KB
- examples/case-studies/case-study-saas-churn.md 8.7 KB
- examples/case-studies/README.md 4.3 KB
- examples/customer-service-roi.json 554 B
- examples/customer-service-triage.json 1018 B
- examples/fintech-fraud-detection.json 1.1 KB
- examples/fintech-fraud-golden-set.json 1.1 KB
- examples/healthcare-patient-triage.json 1.3 KB
- examples/manufacturing-notes.md 2.0 KB
- examples/retail-demand-forecasting.json 1.3 KB
- examples/saas-churn-prediction.json 1.0 KB
- examples/sample-fde-scoping-report.docx 12 KB
- INSTALL.md 2.1 KB
- LICENSE 709 B
- mcp_server/__init__.py 1.2 KB runs code
- mcp_server/__main__.py 950 B runs code
- mcp_server/pyproject.toml 416 B
- mcp_server/README.md 3.6 KB
- mcp_server/server.py 1.9 KB runs code
- mcp_server/tools/__init__.py 608 B runs code
- mcp_server/tools/decompose.py 3.3 KB runs code
- mcp_server/tools/evals.py 1.8 KB runs code
- mcp_server/tools/ontology.py 1.5 KB runs code
- mcp_server/tools/recon.py 1.8 KB runs code
- mcp_server/tools/roi.py 2.2 KB runs code
- mcp_server/tools/scientific_search.py 3.9 KB runs code
- mcp_server/tools/trust_score.py 3.8 KB runs code
- prompts/discovery-interview.md 7.4 KB
- prompts/domain-research.md 6.3 KB
- prompts/strategic-questions.md 6.8 KB
- README.md 2.3 KB
- references/ai-agent-engineering.md 12 KB
- references/arbor-htr-integration.md 1.0 KB
- references/business-ai-upgrade.md 13 KB
- references/eval-rubric.md 6.2 KB
- references/fde-document-output.md 3.1 KB
- references/fde-methodology.md 12 KB
- references/fde-scientific-search.md 4.7 KB
- references/fde-skeptical-deployment.md 3.7 KB
- references/fde-trust-score.md 6.7 KB
- references/industry-benchmarks.md 7.4 KB
- references/saas-playbook.md 12 KB
- references/tech-stacks-2026.md 10 KB
- references/ui-2026-cinematic/effects.css 6.4 KB
- references/ui-2026-cinematic/patterns.js 5.7 KB runs code
- references/ui-2026-cinematic/SKILL.md 6.6 KB
- requirements.txt 215 B
- scripts/arbor_coordinator.py 427 B runs code
- scripts/arbor_fde.py 392 B runs code
- scripts/decompose_problem.py 8.3 KB runs code
- scripts/evals_runner.py 14 KB runs code
- scripts/fde_recon.py 19 KB runs code
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.
- 8d ago First seen · 201 lines · 120 tokens per session scan A 1b059478e9fc
fde-consultant is a skill published in the GitHub repository selectess/fde-consultants-protocoles (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 120 tokens to every session and 2,937 once invoked, about $0.0006 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.
Other skills, from other repositories
extract
Run the full Semantica semantic extraction pipeline on a file or selected text — NER, relations, events, coreference resolution, triplets, and validation. Clears result cache before each run. Returns Markdown tables with entity/relation/event/triplet results and inline validator warnings.
dd-synthesis
Synthesize findings from multiple specialist agents into a coherent investment recommendation. Use when combining reports from 9+ specialist agents into a single decision document.
loop-orchestration
Reference loop-orchestration example; a local loop host chains governed runx turns through receipts, budgets, context, and stop policy.
loop-operator-context
Advisory operating context for the loop-orchestration example.
nitrosend
Operate a Nitrosend account through one governed Runx skill: inspect readiness, analytics, subscription plans, and purchase status; plan and apply campaign/flow/template/segment drafts; import consented contacts; and approve or deliver email operations with provider readback.
issue-intake
Turn a noisy inbound request into a bounded intake artifact and an explicit next runx lane.