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 skills add bearded-illirian/trailmark --skill go-guidegit clone --depth 1 https://github.com/bearded-illirian/trailmarkWrote 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/bearded-illirian/trailmark/go-guide)<a href="https://agentmods.dev/skills/bearded-illirian/trailmark/go-guide"><img src="https://agentmods.dev/badge/skills/bearded-illirian/trailmark/go-guide.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00163 | $0.01791 |
| Opus 5 | $0.00081 | $0.00896 |
| Sonnet 5 | $0.00033 | $0.00358 |
| Haiku 4.5 | $0.00016 | $0.00179 |
Grade A, and why
go-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 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/go-guide — Add a Conceptual Guide
Captures a durable concept — architectural decision, workflow rule, domain vocabulary — into the project's knowledge folder so future readers (including the same person in three months) can rediscover it without digging through commits.
Step 0 — Choose invocation mode
Three modes cover three lifecycles:
| Mode | Trigger | Behavior |
|---|---|---|
| interactive | User types /go-guide |
Full flow, asks project + topic + title + text |
| from-task | $go-guide with (mode='from-task', task_slug=…) |
ship-first hook after fast-track close; suggests title/text from task context, user edits |
| from-epic | $go-guide with (mode='from-epic', epic_slug=…) |
Epic closure hook; same as from-task but scoped to whole epic |
Step 1 — Select project
Read aihub/projects.yml. Show numbered menu of projects. Wait for user
choice or partial-name match.
Save to session context:
{project_id}= chosen project id (slug){project_path}= project's local path{knowledge_root}={project_path}/project-knowledge/guides/
If {project_path} doesn't have project-knowledge/ folder — create it:
mkdir -p "{project_path}/project-knowledge/guides/"
Step 2 — Select topic
A topic is a stable folder grouping guides by subject (e.g.
architecture, workflows, terminology, decisions). Ask the user
which topic; offer existing topics first:
ls "{knowledge_root}" 2>/dev/null
Show numbered menu + 0. New topic. If user picks new — ask for slug
(lowercase, hyphens). Create the folder:
mkdir -p "{knowledge_root}/{topic_slug}/"
Step 3 — Compose title
For interactive mode — ask user for one-line title.
For from-task / from-epic mode — propose a title derived from task/epic slug + brief. Show proposal, wait for user edit or approval.
Convert to filename slug:
"Why we chose SQLite over Postgres" → "why-sqlite-over-postgres.md"
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.
- 4d ago Changed 86d12b230c25
- 8d ago First seen · 250 lines · 163 tokens per session scan A 854d49834709
go-guide is a skill published in the GitHub repository bearded-illirian/trailmark (19 stars, last pushed 6d ago), licensed MIT. It adds 163 tokens to every session and 1,791 once invoked, about $0.0008 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
contract-review
Legal contract analysis using CUAD dataset (41 risk categories). Supports NDA, SaaS, M&A, employment, payment/merchant, and finder/broker agreements. Identifies red flags, suggests redlines, compares to market standards.
call-prep
Call preparation: research, CRM, talking points, PDF.
client-workspace
Create client folder structure in Drive, share docs, check permissions before calls.
confluence-automation
Automate Confluence page creation, content search, space management, labels, and hierarchy navigation via Rube MCP (Composio). Always search tools first for current schemas.
frontmatter-validation
Validate and fix YAML frontmatter metadata in markdown documentation files. Covers required fields, field formats, and schema compliance for SKILL.md and knowledge-copilot files. Use proactively when auditing documentation frontmatter, reviewing SKILL.md files, or fixing YAML metadata errors.
doc
Documentation specialist for README updates, onboarding material, API docs, setup guides, and durable technical explanations.