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 agentmods add skills/dork-labs/dorkos/adding-config-fieldsnpx skills add dork-labs/dorkos --skill adding-config-fieldsgit clone --depth 1 https://github.com/dork-labs/dorkosWrote 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/dork-labs/dorkos/adding-config-fields)<a href="https://agentmods.dev/skills/dork-labs/dorkos/adding-config-fields"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/adding-config-fields.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 | $0.00061 | $0.06451 |
| Opus 5 | $0.00030 | $0.03225 |
| Sonnet 5 | $0.00012 | $0.01290 |
| Haiku 4.5 | $0.00006 | $0.00645 |
Grade A, and why
adding-config-fields 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 — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adding Config Fields in DorkOS
Overview
This skill guides the full lifecycle of changing ~/.dork/config.json (or, post-refactor, ~/.dork/marketplaces.json) schema: Zod field → import-time defaults → conf migration → docs update → tests → CLI flag wiring if applicable. Use it whenever you touch UserConfigSchema so you don't ship a partial change.
DorkOS uses the conf library (v15.1.0) for persistent user configuration, wrapped at apps/server/src/services/core/config-manager.ts. Zod is the authoritative schema and is bridged to conf's Ajv validation via z.toJSONSchema(UserConfigSchema). You do not hand-write JSON Schema; you edit Zod and let the bridge regenerate it.
When to use
- You're about to edit
packages/shared/src/config-schema.ts(adding, renaming, removing, or retyping a field inUserConfigSchema). - You're about to edit
apps/server/src/services/core/config-manager.tsfor any reason related to themigrationsblock orprojectVersion. - (Future) You're about to edit
MarketplacesFileSchemaonceapps/server/src/services/marketplace/marketplace-source-manager.tsis refactored ontoconf. - A user asks "how do I add a setting to DorkOS?" or "how do config migrations work here?"
/system:releasePhase 2 flags a config schema drift and you need to write the migration.
Key concepts
The authoritative files
| File | Role |
|---|---|
packages/shared/src/config-schema.ts |
Authoritative. Zod schema + defaults constant. Change this first. |
apps/server/src/services/core/config-manager.ts |
The conf wrapper. Holds projectVersion + migrations. Change this second. |
contributing/configuration.md |
User-facing settings reference. Update the table + narrative. |
docs/getting-started/configuration.mdx |
External Fumadocs mirror of the same reference. Keep in sync. |
apps/server/src/services/core/__tests__/config-manager.test.ts |
Migration + upgrade-path tests. |
packages/cli/src/cli.ts |
CLI flag wiring (only if the field needs a flag). |
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 · 377 lines · 61 tokens per session scan A a6ecb9ca0477
adding-config-fields is a skill published in the GitHub repository dork-labs/dorkos (9 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 6,451 once invoked, about $0.0003 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
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
openai-whisper-api
Transcribe audio via OpenAI Audio Transcriptions API (Whisper).
perf-code-paths
Use when mapping code paths, entrypoints, and likely hot files before profiling.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
compare-harnesses
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.