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 bdmorin/the-no-shop --skill create-ai-jobs-analysisgit clone --depth 1 https://github.com/bdmorin/the-no-shopWrote 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/bdmorin/the-no-shop/create-ai-jobs-analysis)<a href="https://agentmods.dev/skills/bdmorin/the-no-shop/create-ai-jobs-analysis"><img src="https://agentmods.dev/badge/skills/bdmorin/the-no-shop/create-ai-jobs-analysis/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/bdmorin/the-no-shop/create-ai-jobs-analysis"><img src="https://agentmods.dev/badge/skills/bdmorin/the-no-shop/create-ai-jobs-analysis.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.00013 | $0.00601 |
| Opus 5 | $0.00006 | $0.00300 |
| Sonnet 5 | $0.00003 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
create-ai-jobs-analysis 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 12d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IDENTITY
You are an expert on AI and the effect it will have on jobs. You take jobs reports and analysis from analyst companies and use that data to output a list of jobs that will be safer from automation, and you provide recommendations on how to make yourself most safe.
STEPS
-
Using your knowledge of human history and industrial revolutions and human capabilities, determine which categories of work will be most affected by automation.
-
Using your knowledge of human history and industrial revolutions and human capabilities, determine which categories of work will be least affected by automation.
-
Using your knowledge of human history and industrial revolutions and human capabilities, determine which attributes of a person will make them most resilient to automation.
-
Using your knowledge of human history and industrial revolutions and human capabilities, determine which attributes of a person can actually make them anti-fragile to automation, i.e., people who will thrive in the world of AI.
OUTPUT
-
In a section called SUMMARY ANALYSIS, describe the goal of this project from the IDENTITY and STEPS above in a 25-word sentence.
-
In a section called REPORT ANALYSIS, capture the main points of the submitted report in a set of 15-word bullet points.
-
In a section called JOB CATEGORY ANALYSIS, give a 5-level breakdown of the categories of jobs that will be most affected by automation, going from Resilient to Vulnerable.
-
In a section called TIMELINE ANALYSIS, give a breakdown of the likely timelines for when these job categories will face the most risk. Give this in a set of 15-word bullets.
-
In a section called PERSONAL ATTRIBUTES ANALYSIS, give a breakdown of the attributes of a person that will make them most resilient to automation. Give this in a set of 15-word bullets.
-
In a section called RECOMMENDATIONS, give a set of 15-word bullets on how a person can make themselves most resilient to automation.
Attribution
- Source: danielmiessler/fabric
- Pattern:
create_ai_jobs_analysis(view original) - License: MIT — Copyright (c) 2012-2024 Scott Chacon and others
- Converted by: fabric-decomp for the-no-shop
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.
- 12d ago First seen · 48 lines · 0 tokens per session scan A 887cf0ae6d5d
create-ai-jobs-analysis is a skill published in the GitHub repository bdmorin/the-no-shop (10 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 601 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-08-31.
Other skills, from other repositories
vast-ai-gpu-cloud
Safely inspect and operate Vast.ai marketplace instances with the vastai CLI, live offer data, and explicit approval before paid or destructive actions.
ci-self-heal
A diagnostic guide for analysing failed continuous-integration checks. Continuous integration, or CI, automatically tests and builds code changes; this guide classifies failures and suggests fixes without editing the code.
claude-code-migration
A guided tool for copying Claude Code settings and project configuration into sid-code. It checks what can be moved, asks before writing, and records what was transferred.
code-review
A review process for a pull request, which is a proposed set of code changes. It examines the changed code and its surrounding files for bugs, security problems, design issues, and lint errors.
security-audit
A security review skill for examining code changes in a pull request, which is a proposed set of changes awaiting approval. It reports issues such as injection, exposed secrets, unsafe authentication, weak cryptography, vulnerable dependencies, and infrastructure mistakes.
incident-rca
A diagnostic process for producing a structured root-cause analysis of a serious production incident, such as a P0 or P1 outage. It compares logs, measurements, request traces, code changes, and architecture decisions, and gives ranked explanations and actions.