Borrowing it
Nothing to install: this file belongs to projectbluefin/dakota. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/projectbluefin/dakota/testing/.agents/skills/dakota-factory/SKILL.mdgit clone --depth 1 https://github.com/projectbluefin/dakotaWrote 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/projectbluefin/dakota/dakota-factory)<a href="https://agentmods.dev/skills/projectbluefin/dakota/dakota-factory"><img src="https://agentmods.dev/badge/skills/projectbluefin/dakota/dakota-factory/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/projectbluefin/dakota/dakota-factory"><img src="https://agentmods.dev/badge/skills/projectbluefin/dakota/dakota-factory.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.00036 | $0.00928 |
| Opus 5.5 | $0.00014 | $0.00371 |
| Sonnet 5.5 | $0.00007 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
dakota-factory 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dakota Factory Model
Keep documentation aligned with executable configuration. Correct durable guidance relevant to the task, without requiring a documentation change for every session.
When to Use
- Ending any implementation, debugging, or triage session that revealed non-obvious behavior or traps
- Creating, auditing, or refactoring skills in
.agents/skills/ - Updating architectural docs in
docs/to reflect running truth - Verifying library or CLI syntax against current official documentation
When NOT to Use
- Read-only queries without authorization to change documentation
- Pure dependency version updates handled automatically by Renovate
Core Process
- Check Relevance and Authority: Identify durable errors or missing constraints relevant to the task. Correct existing guidance when edits are authorized; otherwise report the finding without writing files.
- Docs Are the Model:
- Skill files are evergreen procedures, not historical logs, ledgers, or backlogs.
- Do not record session dates (e.g.
2026-08-01: we found X). Extract the timeless rule. - Do not maintain running issue tables or resolved checklists in skills. Gaps belong in GitHub issues; resolved items belong in git history.
- Audit Skill Usability:
Ensure the affected skill in
.agents/skills/contains:- Valid YAML frontmatter with
nameand a descriptivedescription; optional metadata should identify real sources, not unavailable tool requirements ## When to Use## When NOT to Use## Core Process## Invariants/## Rules## Common Rationalizations## Red Flags## Verification
- Valid YAML frontmatter with
- Verify Official Documentation:
- Identify the external tool and the version used by Dakota.
- Read its current official documentation directly, or use Context7 when available.
- Verify the specific syntax or behavior against the pinned source when needed.
- Cite the official URL in relevant guidance or optional
metadata.verified-sources.
- Keep Changes Scoped: Include relevant documentation corrections with the code diff for review. Do not add unrelated writebacks, create a commit, or publish a PR without authorization.
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 Changed · -7 lines · -12 tokens per session 2bff8588dbc5
- 1mo ago First seen · 87 lines · 48 tokens per session scan A d89c148cb99b
dakota-factory is a skill published in the GitHub repository projectbluefin/dakota (193 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 928 once invoked, about $0.0001 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-09-08.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.