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 ambient-code/platform --skill scaffoldgit clone --depth 1 https://github.com/ambient-code/platformWrote 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/ambient-code/platform/scaffold)<a href="https://agentmods.dev/skills/ambient-code/platform/scaffold"><img src="https://agentmods.dev/badge/skills/ambient-code/platform/scaffold/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/ambient-code/platform/scaffold"><img src="https://agentmods.dev/badge/skills/ambient-code/platform/scaffold.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00103 | $0.01150 |
| Opus 5.5 | $0.00041 | $0.00460 |
| Sonnet 5.5 | $0.00021 | $0.00230 |
| Haiku 4.5 | $0.00010 | $0.00115 |
Grade A, and why
scaffold 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 1mo 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold
Generate the complete file set for a new integration, endpoint, or feature flag.
Usage
/scaffold integration <name> # Full integration scaffold
/scaffold endpoint <name> # API endpoint scaffold
/scaffold feature-flag <name> # Feature flag scaffold (delegates to /unleash-flag)
User Input
$ARGUMENTS
Parse the scaffold type and name from $ARGUMENTS. If ambiguous, ask the user.
Integration Scaffold
Based on the established integration pattern (Jira, CodeRabbit, Google Drive), generate the full file set.
Backend Files
| File | Purpose | Template |
|---|---|---|
components/backend/handlers/{provider}_auth.go |
Auth handlers + K8s Secret CRUD | Follow jira_auth.go pattern |
components/backend/handlers/integration_validation.go |
Add validation + test endpoint | Add Validate{Provider} function |
components/backend/handlers/integrations_status.go |
Add to unified status | Add provider to status aggregation |
components/backend/handlers/runtime_credentials.go |
Session credential fetch with RBAC | Add fetch{Provider}Credentials |
components/backend/routes.go |
Register endpoints | Add route group with auth middleware |
Frontend Files
| File | Purpose | Template |
|---|---|---|
components/frontend/src/components/integrations/{provider}-connection-card.tsx |
Integration card UI | Follow existing integration card (e.g., Jira) |
components/frontend/src/services/api/{provider}-auth.ts |
API client | Follow existing auth service pattern |
components/frontend/src/services/queries/use-{provider}.ts |
React Query hooks | Follow existing query hook pattern |
components/frontend/src/app/api/auth/{provider}/route.ts |
Next.js proxy route | Follow existing auth proxy |
components/frontend/src/components/integrations/IntegrationsClient.tsx |
Add card import | Update imports + render |
components/frontend/src/components/integrations/integrations-panel.tsx |
Add to panel | Update panel |
What ships with it
1 file 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.
- 1mo ago First seen · 133 lines · 103 tokens per session scan A a1885dcad76c
scaffold is a skill published in the GitHub repository ambient-code/platform (131 stars, last pushed yesterday), licensed MIT. It adds 103 tokens to every session and 1,150 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
oss-alternatives
Find actively maintained open source alternatives to any paid SaaS tool or commercial API. Use this skill whenever a user mentions wanting to replace, swap out, self-host, or find a free/open source version of a paid tool — including but not limited to tools like Datadog, Algolia, Twilio, Stripe, Auth0, Segment…
contribute-spec-fix
Fix a broken OpenAPI spec in jentic-public-apis with an OpenAPI Overlay, validate it (spectral lint + idempotency check), and contribute it back via a PR to the community catalog. Falls back to applying the same overlay to the local Jentic registry if the user can't wait for maintainer approval, and closes the loop by…
write-microflows
Microflow syntax reference in MDL — every activity type, control flow, expressions, and the mistakes that fail mxcli check. Use before writing any CREATE MICROFLOW, and when debugging a microflow syntax error.
01-bootstrap
Design and validate a new SaaS's architecture into an INSTALL.md via Q&A and stack comparison. Use when the user starts a project, chooses a stack, or picks an architecture pattern. Not for editing an existing stack or scaffolding code.
java-actions
Create and call custom Java actions — extending Mendix with server-side Java, and invoking those actions from microflows in MDL. Use when logic needs a Java library, an algorithm microflows cannot express, or an integration only available in Java.
json-structures-and-mappings
Create and manage JSON structures, import mappings and export mappings in MDL, plus the domain-model shapes they map onto. Use when turning a JSON payload into entities, mapping a REST or queue response, or exporting objects as JSON.