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/nevaberry/nevaberry-plugins/agopengps-knowledge-patchnpx skills add Nevaberry/nevaberry-plugins --skill agopengps-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWrote 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/nevaberry/nevaberry-plugins/agopengps-knowledge-patch)<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/agopengps-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/agopengps-knowledge-patch.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 | $0.00012 | $0.02322 |
| Opus 5 | $0.00006 | $0.01161 |
| Sonnet 5 | $0.00002 | $0.00464 |
| Haiku 4.5 | $0.00001 | $0.00232 |
Grade A, and why
agopengps-knowledge-patch 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 4d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgOpenGPS Knowledge Patch
Use this skill when designing, extending, deploying, or diagnosing AgOpenGPS, AgIO, AgValoniaGPS, AgOpenWeb, GNSS correction paths, autosteer hardware, or machine-control hardware. Start by identifying the exact application release, codebase, board revision, firmware source commit, and operating mode.
Treat application behavior, field data, profiles, wire protocols, and hardware pinouts as separate compatibility surfaces. Shared ancestry or a familiar board name does not make any of those surfaces interchangeable.
Reference index
| Reference | Topics |
|---|---|
| references/architecture-profiles-and-releases.md | WinForms modernization, profiles, section timing, Task Controller, Easy Drive, release selection, field-data fixes |
| references/desktop-operation-and-networking.md | Safety, portable installation, section capacity, layered AgIO diagnosis, Ethernet conventions |
| references/cross-platform-hosts.md | AgValoniaGPS archival, AgOpenWeb architecture, execution modes, artifacts, migration boundaries |
| references/ntrip-and-correction-routing.md | AgIO NTRIP requests, GGA, correction outputs, Serial NTRIP, caster pinning |
| references/rtcm-base-and-rtkbase.md | F9P base messages, MSM coherence, correction freshness, RTKBase relays, receiver profiles |
| references/nmea-and-application-protocol.md | Active sentence dispatch, checksum exception, NMEA/RTCM/custom-PGN boundaries |
| references/autosteer-hardware.md | Hardware levels, AIO revisions, Teensy requirements, steering interfaces, antennas, IMU and WAS setup |
| references/machine-and-rate-control.md | Machine firmware identity, PGNs, rate-controller families, ISOBUS ownership |
What ships with it
9 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.
- coverage.json 1.1 KB
- references/architecture-profiles-and-releases.md 3.1 KB
- references/autosteer-hardware.md 2.9 KB
- references/cross-platform-hosts.md 2.2 KB
- references/desktop-operation-and-networking.md 2.1 KB
- references/machine-and-rate-control.md 2.3 KB
- references/nmea-and-application-protocol.md 1.4 KB
- references/ntrip-and-correction-routing.md 1.3 KB
- references/rtcm-base-and-rtkbase.md 2.4 KB
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.
- 4d ago First seen · 223 lines · 12 tokens per session scan A 7261f2cbea95
agopengps-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (24 stars, last pushed 8d ago), licensed MIT. It adds 12 tokens to every session and 2,322 once invoked, about $0.0001 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
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
maintenance
Investigate, adopt, and verify dependency updates — with special handling for @cyanheads/mcp-ts-core. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or…
report-issue-local
File a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.
api-services
API reference for built-in service providers (LLM, Speech, Graph). Use when looking up service interfaces, provider capabilities, or integration patterns.