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/firstp1ck/pi-coding-agent-forge/raspberrypi-localnpx skills add Firstp1ck/pi-coding-agent-forge --skill raspberrypi-localgit clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-forgeWhat 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.00111 | $0.01815 |
| Opus 5 | $0.00056 | $0.00907 |
| Sonnet 5 | $0.00022 | $0.00363 |
| Haiku 4.5 | $0.00011 | $0.00181 |
Grade A, and why
raspberrypi-local 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Raspberry Pi Documentation Local Wiki
Use the local official Raspberry Pi Documentation corpus before web sources. Optimize for source-backed answers with bounded output and local path citations.
Corpus profile
- Local checkout path:
~/.raspberrypiwiki - Indexed source: official
raspberrypi/documentationrepository, primarilydocumentation/asciidoc/ - Parser/format: AsciiDoc
- Indexed extensions:
.adoc,.asciidoc,.asc - Setup command:
/raspberrypi-wiki-local-setup - Smoke test:
/raspberrypi_wiki-smoke-testorraspberrypi_wiki_smoke_test({ maxSearchResults: 5 })
The repository contains source files used to build the public Raspberry Pi Documentation site. It also has build/tooling Markdown files; the local wiki intentionally indexes only AsciiDoc documentation files to avoid build-doc noise in support searches.
Confidence target
Aim for 90-95/100 confidence by combining local documentation evidence, exact section citations, read-only local evidence when relevant, and explicit caveats when docs/output are incomplete.
If confidence is below 90/100, improve it by searching a second wording, listing sections, extracting exact sections, checking related pages, checking official online docs for freshness, or asking for missing hardware/OS details.
Required workflow
- Start with
raspberrypi_wiki_search({ query, limit: 5, includeSnippets: false }). - If the page is large or aggregate-like, run
raspberrypi_wiki_sections({ page, maxSections: 40-80 }). - Prefer exact section extraction for final evidence:
raspberrypi_wiki_extract({ page, section, maxChars: 4000-8000, maxSections: 2-5 })
- Use query extraction only for exploration, then switch to exact headings when available.
- Use
raspberrypi_wiki_read({ page, maxChars })only for broad context or when no relevant heading is identifiable. - Use
raspberrypi_wiki_related({ page, limit: 5-10 })when the issue spans linked topics. - Run read-only local diagnostics when system/project evidence is relevant.
- Compare documentation guidance with observed local state.
- Cite local paths and section names in final answers.
- Ask before destructive, persistent, hardware-risk, or user-facing changes.
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 · 126 lines · 111 tokens per session scan A 4acc7876aa18
raspberrypi-local is a skill published in the GitHub repository Firstp1ck/pi-coding-agent-forge (74 stars, last pushed 3d ago), licensed MIT. It adds 111 tokens to every session and 1,815 once invoked, about $0.0006 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
opentrons-integration
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
pylabrobot
Vendor-agnostic lab automation framework. Use when controlling multiple equipment types (Hamilton, Tecan, Opentrons, plate readers, pumps) or needing unified programming across different vendors. Best for complex workflows, multi-vendor setups, simulation. For Opentrons-only protocols with official API…
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
flow-nexus-platform
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges.
github-code-review
Comprehensive GitHub code review with AI-powered swarm coordination.
github-multi-repo
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration.