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/mgd34msu/goodvibes-plugin/intel-masterynpx skills add mgd34msu/goodvibes-plugin --skill intel-masterygit clone --depth 1 https://github.com/mgd34msu/goodvibes-pluginWrote 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/mgd34msu/goodvibes-plugin/intel-mastery)<a href="https://agentmods.dev/skills/mgd34msu/goodvibes-plugin/intel-mastery"><img src="https://agentmods.dev/badge/skills/mgd34msu/goodvibes-plugin/intel-mastery.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.00088 | $0.01496 |
| Opus 5 | $0.00044 | $0.00748 |
| Sonnet 5 | $0.00018 | $0.00299 |
| Haiku 4.5 | $0.00009 | $0.00150 |
Grade A, and why
intel-mastery 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
intel-mastery
The goodvibes intel server ships 15 tools. They are opt-in, not mandatory. Reach for one on the operations it is actually measured to beat a native tool on, among them structure-aware search, safe-delete reference checking, and API, schema, and component analysis. Do not force one where a native tool is simpler, or where intel does not cover the case at all.
Fourteen of the fifteen only read. The exception is structural_edit, which writes, and it is
covered at the end of this skill.
The contract every filesystem tool follows
Every tool that touches the filesystem takes base_path and echoes resolved_path (absolute)
for every file in the response. Pass base_path explicitly. A relative path resolved without
one still works, but the response carries a warning field telling you it resolved against the
server's own working directory, which may not be what you meant.
Every response is an envelope: { success, data, error?, warning?, meta }. meta.token_estimate
is computed from the actual rendered response, not a guess. If a cap trimmed the payload,
meta.truncated is true and meta.effective_caps names which cap did it. A response that
silently drops content without saying so is a bug, not intended behavior.
code_read: outline or lines, not everything
Two extract modes: outline (structure: exports, top-level declarations, no bodies) and
lines/range (actual content, optionally with line numbers via include_line_numbers).
Start with outline when you're orienting yourself in a file you haven't read yet; only pull
lines for the specific ranges you need to act on. Batch multiple files in one call. Each
entry in the response is keyed by the request entry, not by path, so two requests for the same
path never collide.
code_grep: the crown jewel, with honest caps
Supports count_only, files_only, and full match output, with real .gitignore respect (not
a partial implementation). Every cap (max_results, max_total_matches) is echoed in
effective_caps in every output format, including count_only. If you get a count, trust it;
if results were capped, truncated says so. Use count_only first to gauge scope on a broad
pattern before pulling full matches.
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 · 116 lines · 88 tokens per session scan A ee905ffbfd2d
intel-mastery is a skill published in the GitHub repository mgd34msu/goodvibes-plugin (6 stars, last pushed 13d ago), licensed MIT. It adds 88 tokens to every session and 1,496 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…