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 jscraik/Agent-Skills --skill talk-moss-skills-team-workflowgit clone --depth 1 https://github.com/jscraik/Agent-SkillsWrote 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/jscraik/agent-skills/talk-moss-skills-team-workflow)<a href="https://agentmods.dev/skills/jscraik/agent-skills/talk-moss-skills-team-workflow"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/talk-moss-skills-team-workflow/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/jscraik/agent-skills/talk-moss-skills-team-workflow"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/talk-moss-skills-team-workflow.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.00067 | $0.00585 |
| Opus 5 | $0.00034 | $0.00293 |
| Sonnet 5 | $0.00013 | $0.00117 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
talk-moss-skills-team-workflow 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Skills to Pay the Bills
Team skills should be decomposed, owned, versioned, evaluated, and maintained like software artifacts.
Read Order
- Use
outline.mdfor the talk thesis, concept map, and safe application boundaries. - Use
quote.mdwhen the answer needs a short supporting excerpt. - Use
transcript.mdonly to confirm what remained after safety redaction. - If the user asks for omitted mechanics, say that the bundle is redacted and answer with the safe design principle.
What This Skill Produces
- team skill workflow
- skill decomposition plan
- eval scenario list
- maintenance checklist
Core Workflow
When answering a factual question:
- Identify the relevant concept from
outline.md. - Answer in 2-5 sentences.
- Add one short excerpt from
quote.mdonly if it strengthens the answer. - State when the bundle does not cover a requested detail.
When applying the talk to the user's work:
- Split overloaded skills into focused capabilities.
- Prefer extension by composition over editing shared instructions blindly.
- Add example scenarios for each skill.
- Assign owner and version policy.
- Review skill quality before reuse.
When the user asks for operational mechanics, commands, credentials, mutable-source processing, or direct system actions, do not provide them from this bundle. Give the design-level alternative instead.
Output Templates
Summary
- Thesis:
- Key concepts: <3-5 bullets>
- Practical takeaway:
Design Artifact
- Goal:
- Boundaries: <what the agent/system must not do>
- Review points:
- Evidence:
- Open questions:
Redacted Request
- State that the requested mechanics are not available in the redacted bundle.
- Explain the risk in neutral terms.
- Provide a safe checklist or conceptual design instead.
What ships with it
4 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.
- 9d ago First seen · 77 lines · 67 tokens per session scan A 73ef88892682
talk-moss-skills-team-workflow is a skill published in the GitHub repository jscraik/Agent-Skills (8 stars, last pushed 11d ago), licensed Apache-2.0. It adds 67 tokens to every session and 585 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-09-03.
Other skills, from other repositories
process-doc
Turn an operational process into a clear SOP, role model, control map, and improvement backlog.
taskuary-setup
Walk the owner through setting Taskuary up - the AI brain, where work arrives, the operator documents, reports and workflows - by reading the install's real state and using the screens that already exist. Use when a task was opened as a Taskuary setup walkthrough.
epic-lead
Use when delivering one approved Kanban EPIC through governed integration, review, and handoff.
teamlead
Use at the START of ANY code task — write/edit/refactor/read code, feature, bug-fix, migration, code investigation. The main thread acts as team-lead, NOT implementer — it delegates work to subagents and surfaces only decisions and results, keeping the main chat clean.
knbn
Alias for the kanban skill. Use when the user invokes or refers to Kanban as "knbn".
foreman-to-issues
Break an approved PRD into small, dependency-ordered, vertically-sliced implementation issues written as local files in the Foreman feature directory. Each issue ships a runnable acceptance check and a declared file footprint. No GitHub, no live quizzing of the user — emits files matching Foreman's issue schema with…