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 press-pass/journalism-skills --skill trusted-human-source-discoverygit clone --depth 1 https://github.com/press-pass/journalism-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/press-pass/journalism-skills/trusted-human-source-discovery)<a href="https://agentmods.dev/skills/press-pass/journalism-skills/trusted-human-source-discovery"><img src="https://agentmods.dev/badge/skills/press-pass/journalism-skills/trusted-human-source-discovery/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/press-pass/journalism-skills/trusted-human-source-discovery"><img src="https://agentmods.dev/badge/skills/press-pass/journalism-skills/trusted-human-source-discovery.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.00010 | $0.00341 |
| Opus 5 | $0.00005 | $0.00170 |
| Sonnet 5 | $0.00002 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
trusted-human-source-discovery 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 10d 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
You will be given a story lead ID. First, call the get_story_leads MCP tool and find the lead matching the provided ID. Read its title, why it matters, and its questions to understand the story.
Using the story, identify 5 people who would be strong human sources to comment on the story. For each person, find their contact information:
- Full name
- Title / role
- Organization
- Email address
- Phone number
- Social media handles (X/Twitter, LinkedIn, etc.)
Prioritize people who are:
- Directly involved in or affected by the story
- Subject matter experts with relevant credentials
- Public officials or spokespeople with relevant authority
- Advocates or community leaders connected to the topic
- Academics or researchers who study the topic
For each source, call the add_source_for_question MCP tool with:
leadId: the story lead IDquestionId: the ID of the question this source is best suited to addressname: the person's full namerelevance: why this person is a good source for this storytitle: their title or roleorganization: their organizationemail: their email addressphone: their phone numbersocialHandles: object with their social media handles (e.g.{"twitter": "@handle", "linkedin": "url"})
After creating all sources, summarize who was found and which questions they were linked to.
Story lead ID: $ARGUMENTS
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.
- 10d ago First seen · 38 lines · 10 tokens per session scan A 8ec90284aff6
trusted-human-source-discovery is a skill published in the GitHub repository press-pass/journalism-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 341 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…