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 OutSystems/outsystems-mcp --skill outsystems-spec-driven-buildgit clone --depth 1 https://github.com/OutSystems/outsystems-mcpWrote 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/outsystems/outsystems-mcp/outsystems-spec-driven-build)<a href="https://agentmods.dev/skills/outsystems/outsystems-mcp/outsystems-spec-driven-build"><img src="https://agentmods.dev/badge/skills/outsystems/outsystems-mcp/outsystems-spec-driven-build/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/skills/outsystems/outsystems-mcp/outsystems-spec-driven-build"><img src="https://agentmods.dev/badge/skills/outsystems/outsystems-mcp/outsystems-spec-driven-build.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.00219 | $0.04564 |
| Opus 5.5 | $0.00088 | $0.01826 |
| Sonnet 5.5 | $0.00044 | $0.00913 |
| Haiku 4.5 | $0.00022 | $0.00456 |
Grade A, and why
outsystems-spec-driven-build 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 today.
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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beta Feature. This skill is a Beta Feature: a non-final OutSystems capability provided to collect customer feedback. It can change significantly, including through breaking changes, or be discontinued. The first time you use this skill in a conversation, tell the user it's a Beta Feature and share https://www.outsystems.com/legal/beta-features-agreement.
OutSystems Spec-Driven Build
Generate a new OutSystems app from a structured, text-only spec via ODC Mentor. The skill's job is the prep step that makes Mentor succeed on the first try: agree a complete spec with the user (roles, data model, screens and who can open each one, what is out of scope), check it, then send it to Mentor with guardrails against the mistakes Mentor commonly makes. Without that, it is just an unguided Mentor prompt.
Load the main outsystems skill before Step 1: session, polling and publish rules come from it (read the live tool catalog, one Mentor session per task, cursor polling and waiting from a fresh context where your harness offers one, the completion signals of a turn, confirm before every tenant write). This skill adds only what is specific to building from a spec; where the two seem to differ, the main skill wins.
Prerequisites
- The
outsystemsMCP server connected and authenticated, per the mainoutsystemsskill. - Mentor enabled on the tenant (this skill drives Mentor).
- A shell with Python 3.8+ to run
scripts/build.py(standard library only). The script never calls the MCP; it handles the spec, the prompts and the report. The commands below saypython3; on Windows usepythonorpy -3ifpython3isn't found. - A target app. Either a new Web app the skill creates (after confirmation) from the standard template, or an empty app the user already created in ODC Studio; see Step 4.
When NOT to use
- Adding features to an existing app → drive Mentor directly with your prompt. Mentor preserves more context with an alive session.
- Building from a design source (Figma, screenshot, HTML mockup, front-end code) → use
outsystems-design-to-app. - Building an app via free-form conversation → drive Mentor directly with your prompt. This skill's value-add is only meaningful when there's a spec to be disciplined about.
- Quick prototyping where you don't care about access rules or quality → this skill's overhead doesn't pay off. A direct Mentor prompt is fine.
What ships with it
6 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.
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.
- today First seen · 197 lines · 219 tokens per session scan A e45995a676d7
outsystems-spec-driven-build is a skill published in the GitHub repository OutSystems/outsystems-mcp (40 stars, last pushed today), licensed MIT. It adds 219 tokens to every session and 4,564 once invoked, about $0.0009 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-10-14.
Other skills, from other repositories
cortex-integrate
Design and implement an AI feature integration — model selection, architecture pattern, system prompt, data flow, error handling, cost estimate. Use when asked to "add AI to this", "LLM integration", "add Claude/GPT", or "AI-powered feature".
spine-api
Design and spec an API — endpoints, request/response shapes, error codes, auth pattern, pagination. Applies Stripe's consistency principles. Use when asked to "design an API", "build API endpoints", "create REST API", or "API for this feature".
spine-design
Produce a system design doc — components, data flow, decisions made, tradeoffs, failure modes. Not a list of options. An actual design with calls made. Use when asked for "system design for", "architect this", "how should we build", or "design the backend".
warden-harden
Produce a hardening spec and implement it — auth patterns, security headers, rate limiting, input validation, secrets management, dependency hygiene. Use when asked to "harden this", "add security to this service", "what security do I need", or "secure this before launch".
spine-perf
Find and fix performance bottlenecks — N+1 queries, missing indexes, sync bottlenecks, caching gaps. Use when asked "why is this slow", "performance issue", "optimize this endpoint", or "N+1 queries".
spine-review
API and backend code review — REST conventions, auth, validation, error handling, pagination, rate limiting, test coverage. Use when asked to "review this API", "code review", "review backend", or "pre-launch backend check".