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 YuDefine/nuxt-supabase-starter --skill specformula-configgit clone --depth 1 https://github.com/YuDefine/nuxt-supabase-starterWrote 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/yudefine/nuxt-supabase-starter/specformula-config)<a href="https://agentmods.dev/skills/yudefine/nuxt-supabase-starter/specformula-config"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/specformula-config/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/yudefine/nuxt-supabase-starter/specformula-config"><img src="https://agentmods.dev/badge/skills/yudefine/nuxt-supabase-starter/specformula-config.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.00040 | $0.01676 |
| Opus 5 | $0.00020 | $0.00838 |
| Sonnet 5 | $0.00008 | $0.00335 |
| Haiku 4.5 | $0.00004 | $0.00168 |
Grade A, and why
specformula-config 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecFormula isa.yml 設定檔指南
isa.yml 是 SpecFormula 測試框架的配置檔,定義 API Spec、Entity Spec 路徑和指令映射。
安裝
依專案語言選擇對應的安裝指南:
- Java → 讀取
java.md
專案結構
src/test/resources/
├── isa.yml # ISA 設定檔
├── specs/
│ ├── api/
│ │ └── api-spec.yml # API Spec(OpenAPI 3.0)
│ └── data/
│ ├── schema.sql # DDL 定義
│ └── entity_to_table_mapping.yml # Entity 對應表
└── features/
└── *.feature # Gherkin 測試檔
完整範例
config:
api:
resource_path: specs/api
project_path: my-project/src/test/resources/specs/api
time_format: iso
data:
permission: isolated
reuse: false
source:
- name: default
resource_path: specs/data
project_path: my-project/src/test/resources/specs/data
db_type: postgresql
instructions:
- name: Time control
format: ^現在的時間是 "(?P<time>.+)"$
instruction_type: time_control
- name: Data preparation
format: ^準備一個(?P<entity>[\u4e00-\u9fffa-zA-Z0-9_]+), with table:$
instruction_type: entity_setup
- name: API call
format: ^\((?:No Actor|UID="(?P<userId>\$[\w.]+)")\) (?P<summary>.+?), call table:$
instruction_type: api_call
- name: Response validation
format: ^(?P<summary>.+?)\((?P<status_code>\d{3})\)回應,?\s*with table:$
instruction_type: response_validate
data_format: data_table
- name: Response validation (JSON)
format: ^(?P<summary>.+?)\((?P<status_code>\d{3})\)回應為,?\s*with JSON:$
instruction_type: response_validate
data_format: json
- name: Database validation
format: ^應該存在一個(?P<entity>[\u4e00-\u9fffa-zA-Z0-9_]+), with table:$
instruction_type: entity_validate
- name: Database non-existence validation
format: ^應該不存在一個(?P<entity>[\u4e00-\u9fffa-zA-Z0-9_]+), with table:$
instruction_type: entity_non_existence_validate
What ships with it
3 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 Changed · -7 lines 0d4f9c1592d0
- yesterday First seen · 173 lines · 40 tokens per session scan A e9abcb6f336a
specformula-config is a skill published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 1,676 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-10.
Other skills, from other repositories
azure-cosmos-db-py
Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service layer classes with CRUD operations, partition key strategies, parameterized queries, or TDD patterns for Cosmos. Triggers…
gh-issue
Size-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file…
product-feature-tech-implement
A development workflow that coordinates separate developer, reviewer, and tester roles to implement a feature design and verify it. TDD, or test-driven development, means using tests as part of guiding the implementation.
prd-v07-implementation-loop
Execute implementation within EPICs following test-first development, continuous SoT updates, and code traceability during PRD v0.7 Build Execution. Triggers on requests to start building, implement an epic, begin coding, or when user asks "start building", "implement epic", "coding", "development", "build execution"…
prd-v07-test-planning
Define test cases BEFORE implementation, ensuring every API, business rule, and user journey has verifiable acceptance criteria during PRD v0.7 Build Execution. Triggers on requests to define tests, plan test coverage, create test cases, or when user asks "define tests", "test planning", "what to test?", "test cases"…
azure-cosmos-db-py
Build production-grade Azure Cosmos DB NoSQL services following clean code, security best practices, and TDD principles.