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 sima-neat/core --skill neat-pcie-application-buildergit clone --depth 1 https://github.com/sima-neat/coreWrote 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/sima-neat/core/neat-pcie-application-builder)<a href="https://agentmods.dev/skills/sima-neat/core/neat-pcie-application-builder"><img src="https://agentmods.dev/badge/skills/sima-neat/core/neat-pcie-application-builder/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/sima-neat/core/neat-pcie-application-builder"><img src="https://agentmods.dev/badge/skills/sima-neat/core/neat-pcie-application-builder.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.00067 | $0.01124 |
| Opus 5.5 | $0.00027 | $0.00450 |
| Sonnet 5.5 | $0.00013 | $0.00225 |
| Haiku 4.5 | $0.00007 | $0.00112 |
Grade A, and why
neat-pcie-application-builder 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 6d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Neat PCIe Application Builder
Overview
Build native host applications against the installed Neat PCIe application APIs. Treat the installed PCIe header, Python module, and packaged tutorials as the source of truth. This is a separate API from the Neat Library used inside the SDK or directly on a DevKit.
The expected input is an MPK model archive or a prepared LLiMa model directory and the requested C++ or Python host application behavior. Follow explicit user requirements when they are compatible with the installed public API; treat the defaults below as guidance.
Choose References
- Read
references/source-of-truth.mdwhen generating or reviewing API use, inspecting an installed release, or resolving version differences. - For MPK model archives, use
pcie::Model. Readreferences/model-lifecycle.mdwhen implementing build, inference, pipelining, cleanup, or multiple-model behavior. - For
pcie::Model, readreferences/tensors-and-images.mdwhen constructing inputs, consuming outputs, handling multiple inputs, or choosing tensor mode versus image mode. - For
pcie::Model, readreferences/model-options.mdwhen configuring a card, queue, preprocessing, MLA-only mode, or object decode behavior. - For prepared LLiMa model directories (LLM, VLM, or ASR), use
pcie::genai::GenAIModeland readreferences/genai.md. Do not apply the MPK build or queue workflow. - Read
references/build-and-validation.mdwhen building, testing, or reporting validation. Do not claim connected-card execution from compile or import checks alone.
Defaults
- For
pcie::Modelin C++, include<simaai/neat/pcie/Model.h>and usesimaai::neat::pcie. For GenAI, include<simaai/neat/pcie/genai/GenAIModel.h>and usesimaai::neat::pcie::genai. - In Python, use
pyneatpcie as pcieforModelorfrom pyneatpcie import genaifor GenAI from the PCIe host Python environment. - In
pcie::Modeltensor mode, inspectmodel.info()before allocating or naming model-ready inputs. In image mode, treat that information as the card-side preprocessing output contract, not the submitted image contract. - For
pcie::Model, enablemla_onlyonly when the application owns the model's dtype conversion; thenmodel.info()is the MLA's own contract and, for INT8 tensors, itsquantparameters are the only valid source for the conversion. - Use
run()for ordinary request/response inference. Usepcie::Modelpush()/pull()for bounded pipelining, or GenAIstream()for incremental output and cancellation. - For performance-sensitive
pcie::Modeltensor pipelines, prefer a bounded ring of reusable contiguous input buffers. Wrap C++ storage withTensor::from_external()or Python arrays withTensor.from_numpy(..., copy=False), and recycle a buffer only after its matching result is pulled. Use simpler owning or copying constructors when reuse and staging overhead do not matter. - Use finite startup and inference timeouts in applications that must fail predictably.
- Close every opened model on normal and error paths. Prefer a Python context manager.
What ships with it
8 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.
- 6d ago Changed · +6 lines · -1 tokens per session d80eee9724a4
- 1mo ago Changed · +8 lines · -9 tokens per session 701d906640b2
- 2mo ago First seen · 63 lines · 77 tokens per session scan A 13544c2320e9
neat-pcie-application-builder is a skill published in the GitHub repository sima-neat/core (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 67 tokens to every session and 1,124 once invoked, about $0.0003 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-08-31.
neat-pcie-application-builder compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| neat-pcie-application-buildersima-neat/core | Skill | 8 | yesterday | Apache-2.0 | A | 67 | Codex |
| gke-compute-classesgoogle/skills | Skill | 22k | yesterday | Apache-2.0 | A | 83 | Claude Code, Codex |
| jetson-diagnosticNVIDIA/skills | Skill | 3.9k | yesterday | Apache-2.0 | A | 30 | Claude Code, Codex |
| holoscan-install-wheelNVIDIA/skills | Skill | 3.9k | yesterday | Apache-2.0 | A | 34 | Claude Code, Codex |
| offensive-z-waveSnailSploit/Claude-Red | Skill | 10k | 25d ago | MIT | A | 113 | Claude Code, Codex |
| doca-socket-relayNVIDIA/skills | Skill | 3.9k | yesterday | Apache-2.0 | A | 236 | Claude Code, Codex |
| hsb-flashNVIDIA/skills | Skill | 3.9k | yesterday | Apache-2.0 | B | 94 | Claude Code |