Borrowing it
Nothing to install: this file belongs to sima-neat/core. 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/sima-neat/core/main/.github/issue-triage/skills/core-triage/SKILL.mdgit 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/core-triage)<a href="https://agentmods.dev/skills/sima-neat/core/core-triage"><img src="https://agentmods.dev/badge/skills/sima-neat/core/core-triage.svg" alt="Measured on agentmods" 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.00000 | $0.01943 |
| Opus 5 | $0.00000 | $0.00971 |
| Sonnet 5 | $0.00000 | $0.00389 |
| Haiku 4.5 | $0.00000 | $0.00194 |
Grade A, and why
core-triage 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
core-triage
Use this skill when triaging GitHub issues in the sima-neat/core
repository.
Repository Scope
core is the SiMa NEAT framework repository. It covers the public C++ API,
Python bindings, graph/model/tensor/sample abstractions, pipeline construction,
runtime orchestration, diagnostics, tutorials, documentation, release artifacts,
and tests for the NEAT developer experience.
Core issues may describe behavior in source builds, installed SDK environments, DevKit execution, documentation, examples, Python packaging, model archive handling, or generated GStreamer pipelines.
First Pass
Before classifying the issue, check whether it is likely a duplicate of an existing issue from the provided issue context. Compare the title, error text, affected API or tutorial, command output, model/package reference, and reported environment against existing discussion in the issue thread and any available repo context.
If the issue appears to duplicate another issue, do not propose closing it and
do not use the duplicate label. Set needs_human_review to true, keep the
primary category aligned with the underlying problem, and mention in the public
comment that it may overlap with an existing report if the evidence is strong.
If the duplicate relationship is uncertain, ask for the missing detail needed to
confirm whether it is the same failure mode.
Safety And Sensitivity
If the issue appears security-sensitive, customer-confidential, or likely to
contain private customer assets, set needs_human_review to true, keep the
public comment conservative, and do not request extended analysis.
Do not ask the reporter to upload private models, customer videos, credentials, tokens, proprietary logs, or full device images. Ask for redacted command output, minimal reproductions, public model references, and version information instead.
sima-neat/internals is private and is not in the cross-reference allowlist. If
an issue likely requires internals/plugin/runtime implementation inspection,
route it to human review rather than requesting extended analysis.
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 First seen · 218 lines · 0 tokens per session scan A 674f930ffdbc
core-triage is a skill published in the GitHub repository sima-neat/core (5 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,943 tokens. 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.