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.
git clone --depth 1 https://github.com/neurofoo/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/commands/neurofoo/agent-skills/jobs)<a href="https://agentmods.dev/commands/neurofoo/agent-skills/jobs"><img src="https://agentmods.dev/badge/commands/neurofoo/agent-skills/jobs.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.1 | $0.00000 | $0.00831 |
| Opus 5 | $0.00000 | $0.00415 |
| Sonnet 5 | $0.00000 | $0.00166 |
| Haiku 4.5 | $0.00000 | $0.00083 |
Grade A, and why
jobs 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- jtbd — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jobs to Be Done Analysis
Analyze a product, feature, or situation through the Jobs to Be Done framework to understand what customers really want.
Instructions
Identify the underlying jobs customers are trying to accomplish, including functional, emotional, and social dimensions. Consider the full context of when and why they "hire" solutions.
Output Format
Subject: [Product/feature/situation being analyzed]
The Context
When does the job arise? [Describe the triggering situation or circumstance]
Who has this job? [Customer segments or personas]
How are they currently solving it? [Existing solutions, competitors, or workarounds]
Job Statement
Core Job
When [situation], I want to [motivation], so I can [expected outcome].
Job Dimensions
Functional Job
The practical task they're trying to complete
| Job | Importance | Current Solution |
|---|---|---|
| [functional job 1] | High/Med/Low | [how they do it now] |
| [functional job 2] | High/Med/Low | [how they do it now] |
Emotional Job
How they want to feel
| Feeling They Want | Feeling They Want to Avoid |
|---|---|
| [positive emotion] | [negative emotion] |
| [positive emotion] | [negative emotion] |
Social Job
How they want to be perceived
| How They Want to Be Seen | By Whom |
|---|---|
| [perception] | [audience] |
| [perception] | [audience] |
Hiring Criteria
What would make them "hire" this solution?
| Criteria | Weight | Notes |
|---|---|---|
| [criterion] | High/Med/Low | [context] |
| [criterion] | High/Med/Low | [context] |
What would make them "fire" it?
| Deal Breaker | Why |
|---|---|
| [issue] | [explanation] |
| [issue] | [explanation] |
Forces Analysis
Forces pushing toward change
| Force | Strength |
|---|---|
| Push: Frustration with current solution | [description] |
| Pull: Attraction of new solution | [description] |
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.
- 7d ago First seen · 140 lines · 0 tokens per session scan A 098003449c3f
jobs is a command published in the GitHub repository neurofoo/agent-skills (111 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 831 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.