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-buildstream/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-buildstream)<a href="https://agentmods.dev/skills/projectbluefin/dakota/dakota-buildstream"><img src="https://agentmods.dev/badge/skills/projectbluefin/dakota/dakota-buildstream/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-buildstream"><img src="https://agentmods.dev/badge/skills/projectbluefin/dakota/dakota-buildstream.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.00037 | $0.00994 |
| Opus 5 | $0.00018 | $0.00497 |
| Sonnet 5 | $0.00007 | $0.00199 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
dakota-buildstream 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 yesterday.
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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dakota BuildStream
Dakota builds the bootc desktop image entirely from source using BuildStream 2. Never translate RPM, DNF, COPR, or Containerfile workflows into this repository.
When to Use
- Creating, editing, or removing
.bstelements inelements/ - Modifying
project.confor junction configurations (elements/gnome-build-meta.bst,elements/freedesktop-sdk.bst) - Managing downstream patches in
patches/ - Triaging build, sandbox, or artifact cache failures in local runs or CI
When NOT to Use
- Workstation Homebrew integration → load
dakota-workstation - End-user ujust recipes → load
dakota-ujust - GNOME Shell extensions packaging → load
dakota-extensions - Image layer composition and boot verification → load
dakota-image
Core Process
- Inspect Graph: Run
just bst show --deps all <element>to trace dependencies and dependents. - Consult Nearest Pattern: Check elements with similar build systems (
manual,autotools,meson,cmake). - Verify Syntax: Check syntax against official BuildStream documentation (
/apache/buildstream). - Implement Deterministically: Ensure build/install steps are reproducible (no network, timestamps, or host identity).
- Validate Graph: Run
just validate. For element-specific tests, build the narrowest target (just bst build <element>). - Patch Hygiene: For junction patches, update
patches/, verify withjust patch-drift-check, and setUpstream-Status:headers.
Invariants
- Compose vs Stack:
kind: composegenerates layer filesystem artifacts.kind: stackonly aggregates dependencies and outputs zero filesystem files. - No Post-Install Packaging: All runtime software must be integrated via BST elements before OCI composition.
- Junction Patches: Patch junctions via
kind: patch_queuesources. Never modify.bst/staged-junctions/. - Source Pinning: Pin git sources to commit SHAs or release tags. Never track mutable branches in production elements.
- Reproducibility: No network calls,
$(date),$(hostname),whoami, or random seeds in build commands. - Directory Creation: Run
mkdir -pbefore creating links or writing files into target directories. - Generated Cargo Sources: Generate crate manifests via:
python3 files/scripts/generate_cargo_sources.py path/to/Cargo.lock
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.
- yesterday Changed · +24 lines 9468c31b74d6
- 10d ago First seen · 57 lines · 37 tokens per session scan A 9fa8ac72469b
dakota-buildstream is a skill published in the GitHub repository projectbluefin/dakota (150 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 994 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…