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/specsnl/agent-specs/linear-intakenpx skills add specsnl/agent-specs --skill linear-intakegit clone --depth 1 https://github.com/specsnl/agent-specsWrote 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/specsnl/agent-specs/linear-intake)<a href="https://agentmods.dev/skills/specsnl/agent-specs/linear-intake"><img src="https://agentmods.dev/badge/skills/specsnl/agent-specs/linear-intake.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.00067 | $0.01180 |
| Opus 5 | $0.00034 | $0.00590 |
| Sonnet 5 | $0.00013 | $0.00236 |
| Haiku 4.5 | $0.00007 | $0.00118 |
Grade A, and why
linear-intake 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 3d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linear Intake Skill — {{CLIENT_NAME}} ({{OUTPUT_TEAM}})
Converts raw {{INPUT_LANGUAGE}} client input (WhatsApp, email, verbal, or a Linear issue URL) into a properly structured Linear issue in {{OUTPUT_LANGUAGE}} for the {{CLIENT_NAME}} development team.
Fixed context
- Source team:
{{INPUT_TEAM}} - Destination team:
{{OUTPUT_TEAM}} - Language: {{PRESERVED_TERMS_NOTE}}
- Audience: the developer reading the ticket should be able to start immediately
Specs rules
General rules
- Short and dense. No fluff, no preamble.
- Markdown. Use
codefor field/table/column/UI names. Use bold for key constraints.
Feature request → IST/SOLL (small) or Current/Want (larger)
Small change — IST/SOLL:
IST:
- [what exists now]
SOLL:
- [what should happen]
[1-2 sentences of context only if non-obvious]
## Acceptance criteria
- [ ] [specific, testable condition]
- [ ] [specific, testable condition]
## QA
- [how to verify the result — steps a tester should follow]
- [edge cases to check]
Larger feature — structured sections:
## Current situation
- [what exists now]
- [relevant context]
## What we want
- [desired behavior]
- [scope or constraints]
- sub-detail if needed
## Why / context
[1-2 sentences, skip if obvious]
## Acceptance criteria
- [ ] [specific, testable condition]
- [ ] [specific, testable condition]
## QA
- [how to verify the result — steps a tester should follow]
- [edge cases to check]
Bug report
[One-line summary of what's wrong]
Steps / context:
- [where to look or how to reproduce]
- [what happens]
- [what should happen instead]
## Acceptance criteria
- [ ] [condition that confirms the bug is fixed]
## QA
- [how to verify the fix]
- [regression checks if relevant]
## Screenshots
[attach any relevant screenshots here]
Operational task (content, newsletter, images)
[Short imperative title: "Prepare April newsletter for sending"]
Deliverables:
- [list attachments/content/actions]
- Deadline: [if mentioned]
Operational tasks don't need acceptance criteria or QA sections.
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.
- 3d ago First seen · 159 lines · 67 tokens per session scan A 11994125884b
linear-intake is a skill published in the GitHub repository specsnl/agent-specs (2 stars, last pushed 18d ago), licensed MIT. It adds 67 tokens to every session and 1,180 once invoked, about $0.0003 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
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
diagnostic-stem-delivery
Audio production with diagnostic analysis, timecode parsing from documents, and verified export workflow.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.