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 rpraharaj/forward-deployed-engineer --skill nfr-validationgit clone --depth 1 https://github.com/rpraharaj/forward-deployed-engineerWrote 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/rpraharaj/forward-deployed-engineer/nfr-validation)<a href="https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/nfr-validation"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/nfr-validation.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.00104 | $0.01789 |
| Opus 5 | $0.00052 | $0.00894 |
| Sonnet 5 | $0.00021 | $0.00358 |
| Haiku 4.5 | $0.00010 | $0.00179 |
Grade A, and why
nfr-validation 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 7d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NFR validation
Measuring what was promised.
Why this exists
nfr-baseline writes down the targets. This skill finds out whether they hold.
The gap between the two is where a specific and common failure lives: everyone agrees performance matters, a target gets written, nobody measures it, and at go/no-go someone says "performance should be fine" — which is a feeling, not evidence, and it is accepted because the alternative is delaying the release to find out.
An FDE is well placed to break that pattern, precisely because you have no stake in the previous assumption. "We haven't measured it" is easier to say when you weren't the one who didn't measure it.
The other half of this skill is failure behavior. Systems are almost never tested for how they behave when a dependency is down, and that is exactly the condition under which they'll be judged.
When this applies
- Before release, against declared NFRs
- Someone claims performance is fine without a number
- A change board needs evidence, not assurance
- You need to know what happens when a dependency fails
- A change alters data volume, query shape, or call patterns
When it doesn't
- No NFRs declared — run
nfr-baselinefirst, or you're measuring against nothing - Genuinely trivial internal tooling
- Production is down or customers are failing now — that's
incident-triage. Coming back later to measure a slow path is this skill.
Prerequisites
.fde/03b-nfrs.md— required. The targets and the baseline..fde/07-verification.md— this appends to it. If the file does not exist, create it with the standard header and say so in Confidence; do not pretendverification-planalready ran.- Access to a realistic environment, or an honest statement that you don't have one
Procedure
1. Measure the same way the baseline was measured
If the baseline came from an APM p95 over thirty days, a local benchmark is not comparable and the comparison will mislead. Match the method, the percentile, and the conditions — or state plainly that you didn't and that the numbers aren't directly comparable.
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.
- 7d ago First seen · 139 lines · 104 tokens per session scan A 7bea5f3106cb
nfr-validation is a skill published in the GitHub repository rpraharaj/forward-deployed-engineer (6 stars, last pushed 20d ago), licensed MIT. It adds 104 tokens to every session and 1,789 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.
Other skills, from other repositories
typescript-providers
Implement, modify, test, or document TypeScript provider packages under ts/packages/providers, including framework adapters for OpenAI, Anthropic, Google, LangChain, Mastra, Vercel, LlamaIndex, Cloudflare, and Claude Agent SDK. Use for provider-specific TS work; do not use for core-only changes.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
python-sdk
Implement or modify Python SDK behavior under python/composio, including tools, toolkits, sessions, auth configs, connected accounts, client integration, and shared Python models. Use for Python core runtime/API work; pair with python-testing and cross-sdk-parity when TypeScript must match.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.