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 Nolane-x/forge-os --skill designing-api-developer-portalgit clone --depth 1 https://github.com/Nolane-x/forge-osWrote 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/nolane-x/forge-os/designing-api-developer-portal)<a href="https://agentmods.dev/skills/nolane-x/forge-os/designing-api-developer-portal"><img src="https://agentmods.dev/badge/skills/nolane-x/forge-os/designing-api-developer-portal.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.00043 | $0.01573 |
| Opus 5 | $0.00022 | $0.00787 |
| Sonnet 5 | $0.00009 | $0.00315 |
| Haiku 4.5 | $0.00004 | $0.00157 |
Grade A, and why
designing-api-developer-portal 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 3d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designing Api Developer Portal
Overview
This skill owns one bounded responsibility: designing api developer portal. Its focus is designing api developer portal within api-products product boundaries. It converts declared inputs into typed artifacts and reproducible evidence without silently changing product scope.
Trigger
Activate only when the project is in one of these stages: product-definition, ux-design, architecture, planning, implementation, verification, release-readiness, all contract preconditions pass, and the router identifies a missing output this skill can produce. Do not activate merely because the skill name resembles the user request.
Required Inputs
product-definition- Optional:
architecture-decision - Optional:
verified-build - Current gate result, open findings, artifact hashes, and invalidation state
- Required tools: none
- Optional tools: none
- Confirmed human decisions relevant to this scope
Method-Specific Protocol
- Define the exact decision, actors, objects, states, invariants, side effects, and non-goals owned by designing api developer portal.
- Build a decision table for normal, boundary, invalid, permission, failure, retry, recovery, concurrency, migration, and abuse conditions relevant to designing api developer portal.
- Apply designing api developer portal only to direct input artifacts; record assumptions, rejected alternatives, and any human decision still required.
- Trace the resulting contract to user value, security, reliability, cost, operability, and downstream consumers.
- Create reproducible checks that would fail if designing api developer portal were incomplete or implemented incorrectly.
Procedure
- Read the confirmed product definition, domain context, assurance profile, and active findings.
- Identify the domain objects, actors, state transitions, regulations, provider boundaries, and operational constraints owned by this skill.
- Define the exact decision, actors, objects, states, invariants, side effects, and non-goals owned by designing api developer portal.
- Build a decision table for normal, boundary, invalid, permission, failure, retry, recovery, concurrency, migration, and abuse conditions relevant to designing api developer portal.
- Apply designing api developer portal only to direct input artifacts; record assumptions, rejected alternatives, and any human decision still required.
- Trace the resulting contract to user value, security, reliability, cost, operability, and downstream consumers.
- Create reproducible checks that would fail if designing api developer portal were incomplete or implemented incorrectly.
- Model normal, boundary, failure, recovery, permission, concurrency, migration, and abuse behavior before implementation.
- Define stable contracts and explicit non-goals; do not leak domain concerns into unrelated modules.
- Create executable acceptance, negative, resilience, and compatibility checks proportional to risk.
- Publish the domain artifact, evidence packet, unresolved assumptions, and downstream invalidations.
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.
- 3d ago First seen · 136 lines · 43 tokens per session scan A f7280e67ec24
designing-api-developer-portal is a skill published in the GitHub repository Nolane-x/forge-os (10 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 1,573 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
design-patterns
Agents should invoke this skill when choosing patterns, designing traits/interfaces/components, deciding abstraction boundaries, evaluating dependency injection/callbacks, or comparing implementation approaches in Rust, TypeScript/React, or Django/Python.
supabase-nextjs
Next.js with Supabase and Drizzle ORM.
architecture-patterns
Software architecture patterns and best practices.
backend-development
A general guide for building backend services, which are the server-side programs that handle data, business rules, and APIs. It switches between Python, Node.js, Go, and Java guidance based on the requested technology.
api-provider-setup
A set of instructions for adding third-party API providers to OpenClaw, an agent platform, through custom model endpoints that follow Anthropic- or OpenAI-compatible formats.
code-to-image
A method for turning HTML, CSS, JavaScript, Canvas, or SVG designs into image files by rendering them in a browser. It uses Playwright, a tool for controlling a browser without a visible window.