Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sima-neat/corenpx agentmods add skills/sima-neat/core/sima-contribute-to-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/sima-contribute-to-neat-core)<a href="https://agentmods.dev/skills/sima-neat/core/sima-contribute-to-neat-core"><img src="https://agentmods.dev/badge/skills/sima-neat/core/sima-contribute-to-neat-core/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/sima-contribute-to-neat-core"><img src="https://agentmods.dev/badge/skills/sima-neat/core/sima-contribute-to-neat-core.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.00073 | $0.01274 |
| Opus 5 | $0.00036 | $0.00637 |
| Sonnet 5 | $0.00015 | $0.00255 |
| Haiku 4.5 | $0.00007 | $0.00127 |
Grade A, and why
sima-contribute-to-neat-core 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 12d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contribute To Neat Core
Use this skill as the operating checklist before changing the Neat framework. The repo optimizes for deterministic pipelines, structured diagnostics, stable public APIs, and agent-friendly development loops.
For deeper architecture notes distilled from the architect-level PDF, read references/architecture-rules.md when touching include/, src/, python/, tests/, tutorials/, or model/pipeline behavior.
First Pass
- Read the local guardrails first:
AGENTS.mddocs/develop-apps/contribute/start-here/coding_standard.mddocs/develop-apps/contribute/build-test/test_requirements.mddocs/develop-apps/contribute/start-here/architecture.md
- Classify the change:
- Public API: anything under
include/*. - Runtime/pipeline:
src/pipeline,src/gst,src/nodes,src/model. - Python API:
python/,pyneat, nanobind bindings. - Docs/tutorials:
docs/,tutorials/, examples, generated tutorial docs.
- Public API: anything under
- Preserve existing patterns before introducing abstractions. Search with
rgfor nearby implementations, tests, and docs.
Core Invariants
- Treat
include/*as stable API. Prefer additive changes. Breaking public signatures require PR documentation, migration notes, tests, and explicit maintainer approval. - Keep module boundaries intact:
builder/must stay STL-only and must not depend on GStreamer orpipeline/.gst/must not depend onpipeline/.nodes/must not depend onpipeline/.pipeline/orchestrates and may depend ongst/,builder/,nodes/,contracts/,policy/, andmodel/.
- Keep behavior deterministic: stable element names, stable pipeline strings, stable report fields, reproducible tests.
- Prefer fail-fast structured errors over hidden fallback. Do not silently convert formats, auto-degrade hardware paths, or mask caps/plugin/runtime failures.
- Keep teardown bounded. Never add indefinite waits in
Run, streaming, bus, or teardown paths. - Keep probe/streaming-thread work lightweight and thread-safe. Diagnostics updated from streaming threads need atomics or equivalent protection.
What ships with it
2 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.
- 12d ago First seen · 93 lines · 73 tokens per session scan A e1f0efa61f09
sima-contribute-to-neat-core is a skill published in the GitHub repository sima-neat/core (5 stars, last pushed today), licensed Apache-2.0. It adds 73 tokens to every session and 1,274 once invoked, about $0.0004 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-31.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…