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 gtmagents/gtm-agents --skill reference-opsgit clone --depth 1 https://github.com/gtmagents/gtm-agentsWrote 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/gtmagents/gtm-agents/reference-ops)<a href="https://agentmods.dev/skills/gtmagents/gtm-agents/reference-ops"><img src="https://agentmods.dev/badge/skills/gtmagents/gtm-agents/reference-ops/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/gtmagents/gtm-agents/reference-ops"><img src="https://agentmods.dev/badge/skills/gtmagents/gtm-agents/reference-ops.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.00017 | $0.00253 |
| Opus 5 | $0.00009 | $0.00127 |
| Sonnet 5 | $0.00003 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
reference-ops 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 9d 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.
What it actually says
Reference Operations Skill
When to Use
- Running reference matching, scheduling, and follow-up processes.
- Auditing reference utilization, fatigue, and consent records.
- Reporting on advocacy impact for sales leadership.
Framework
- Request Intake – standardize forms, qualification criteria, and SLA expectations per deal stage.
- Matching Logic – map requests to advocates by persona, industry, use case, language, and availability.
- Logistics & Compliance – schedule calls, provide briefing docs, capture approvals, and log NDAs.
- Post-call Workflow – collect feedback from both parties, update CRM entries, and issue rewards.
- Analytics & Governance – monitor utilization, fatigue thresholds, and gaps by segment.
Templates
- Reference request form template.
- Matching matrix (request attributes → advocate tags).
- Follow-up checklist and feedback survey.
Tips
- Integrate with CRM to auto-create tasks and close the loop with reps.
- Flag overused advocates and rotate in new voices regularly.
- Share monthly scorecards with GTM teams to highlight wins and needs.
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.
- 9d ago First seen · 31 lines · 17 tokens per session scan A 1056199d0dd7
reference-ops is a skill published in the GitHub repository gtmagents/gtm-agents (399 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 253 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-09-03.
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…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.