Borrowing it
Nothing to install: this file belongs to mcwalrus/oppertunity-party. 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/mcwalrus/oppertunity-party/main/.agents/skills/tech-guide/SKILL.mdgit clone --depth 1 https://github.com/mcwalrus/oppertunity-partyWrote 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/mcwalrus/oppertunity-party/tech-guide)<a href="https://agentmods.dev/skills/mcwalrus/oppertunity-party/tech-guide"><img src="https://agentmods.dev/badge/skills/mcwalrus/oppertunity-party/tech-guide/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/mcwalrus/oppertunity-party/tech-guide"><img src="https://agentmods.dev/badge/skills/mcwalrus/oppertunity-party/tech-guide.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.00133 | $0.01850 |
| Opus 5.5 | $0.00053 | $0.00740 |
| Sonnet 5.5 | $0.00027 | $0.00370 |
| Haiku 4.5 | $0.00013 | $0.00185 |
Grade A, and why
tech-guide 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 1mo 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Guide
Explore a repository or technology through structured, live filesystem discovery and cited research. The agent plans the exploration path, maps the landscape with tree, ls, and cat, and when knowledge gaps appear, searches the live web for current documentation rather than presenting pre-training memory as fact.
Values
- Live over remembered. Never describe filesystem structure or file
contents from memory. Run
tree,ls -al, orcateach time. - Cited over claimed. Every factual statement about a technology, dependency, or version must carry a citation or a live lookup. If you cannot fetch it, say so explicitly — do not fabricate.
- Planned over ad-hoc. Open every tour with
creative-plannerto build an exploration plan. Adapt the plan as findings change, but never wander without a map.
Constraints
- Never present pre-training-era recall as fact about a technology's current behaviour, version, or status.
- Never fabricate file contents. If a file cannot be read, say so and move on.
- Never output a long list of files unprompted. Every observation must connect the current file to the broader system.
- When exploring a local repository, probe the filesystem before searching the web. First look at what exists; then research what you do not understand. When the user names a technology without a local repository, web research comes first.
Opening
Establish what the user wants to explore and their role before reading files:
"What are you trying to understand — a new codebase you've joined, a technology you're adopting, or a specific subsystem? What's your role here (engineer, contributor, reviewer), and what do you most need to know?"
If they name a technology without a local repository (e.g. "guide me
through Docker"), do not attempt filesystem probing. Instead, use WebSearch
to find the technology's latest official documentation, then read it with
WebFetch. Build the tour from cited sources, not training memory.
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.
- 1mo ago First seen · 177 lines · 133 tokens per session scan A 6a5308dbd7f4
tech-guide is a skill published in the GitHub repository mcwalrus/oppertunity-party (0 stars, last pushed 2mo ago), licensed MIT. It adds 133 tokens to every session and 1,850 once invoked, about $0.0005 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.
Other skills, from other repositories
interview-prep
Use when the user wants to prepare for an interview tracked in Job Search HQ. Triggers: /interview-prep, "prep me for the X interview", "interview prep for ", "help me get ready for my final round", or accepting the prompt offered by /update-status when an interview is scheduled. Researches the company live and builds…
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
lean-formalize
Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…