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 blisspixel/primr --skill company-researchgit clone --depth 1 https://github.com/blisspixel/primrWrote 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/blisspixel/primr/company-research)<a href="https://agentmods.dev/skills/blisspixel/primr/company-research"><img src="https://agentmods.dev/badge/skills/blisspixel/primr/company-research/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/blisspixel/primr/company-research"><img src="https://agentmods.dev/badge/skills/blisspixel/primr/company-research.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.00037 | $0.01055 |
| Opus 5 | $0.00018 | $0.00528 |
| Sonnet 5 | $0.00007 | $0.00211 |
| Haiku 4.5 | $0.00004 | $0.00105 |
Grade A, and why
company-research 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Company Research
Purpose
Use this skill to start and monitor Primr research runs through MCP. Treat MCP as the source of truth for current modes, defaults, and outputs.
Workflow
-
Read
primr://research/modesto confirm the current mode guidance. -
Read
primr://research/statusto see whether a run is already active. -
Call
estimate_runbefore starting a new run. Supportsplatforms(array),strategy_type, andno_ai_strategyparameters. Returnsestimated_time_rangealongsideestimated_time_minutes. -
Present the estimate, state that the run incurs real API cost, and get explicit approval before calling
research_company. -
After starting a run, monitor with
wait_for_status_changeorcheck_jobsuntil terminal. -
Read
primr://output/artifacts/by_job/{job_id}to inventory completed-job artifacts without report body content, then readprimr://output/latestonly when a report preview is needed to present the result and next actions. Readprimr://output/qa_summary/by_job/{job_id}when QA artifacts are attached and the user needs QA outcome metadata. Readprimr://output/usage_summary/by_job/{job_id}when the user needs cost, timing, approval, or artifact-count metadata. Readprimr://output/source_summary/by_job/{job_id}when the user needs citation/source appendix metadata. Readprimr://output/trace_summary/by_job/{job_id}when the user needs scrape trace health metadata. Readprimr://output/verification_summary/by_job/{job_id}when the user needs claim verification trust score, claim counts, status counts, first-party downgrade counts, or source-reference counts without raw claims, source URLs, search queries, explanations, or report body content. Readprimr://output/calibration_summary/by_job/{job_id}when the user needs label-calibration counts, inference source-copy counts, evidence-review count buckets, judge provenance, or judge-agreement metadata without raw claims, source URLs, evidence reviews, rationales, or report body content. MCP resource reads are audit-logged with hashed URI/result values and normalized resource kind, without raw URI query values or resource bodies. A2A skill calls are audit-logged with hashed message/result payloads, hashed caller ids, granted scopes, duration, outcome, and job id when present, without raw message text, task ids, URLs, report paths, raw results, or caller ids.
What ships with it
1 file 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 · 152 lines · 37 tokens per session scan A 8962afe760c7
company-research is a skill published in the GitHub repository blisspixel/primr (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 37 tokens to every session and 1,055 once invoked, about $0.0002 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
vaaya
Vaaya is the payment system for agents: one MCP server that lets your agent call paid APIs pay-per-call with no API keys. Web search, scraping, image and video generation, code sandboxes, browser automation, email, phone calls, lead enrichment, live data. Priced in cents per call, billed only on success, and every…
autosearch:channel-selection
Group-first channel selection algorithm for v2 tool-supplier architecture. Given a research query + clarify rubrics + channelpriority hints, picks 1-3 relevant groups from the router index, then 3-8 leaf channels from within those groups. Replaces flat-rank selection across 41 channels with a two-stage pick so runtime…
autosearch:citation-index
Deduplicate URLs across all sources, assign stable citation numbers, and merge citations from multiple subagents / sections into one consistent reference list. Prevents "same URL cited as [3] in one paragraph and [17] in another" and "different URLs merged under [5]" bugs that come from per-section synthesis.
autosearch:context-retention-policy
Session-level policy for keeping the runtime AI's context window healthy across long research — keep-last-k tool results, offload older evidence to disk, trigger compaction at thresholds. Borrows MiroThinker's keeptoolresult, deepagents' summarization middleware, and deer-flow's SummarizationEvent pattern. Orthogonal…
autosearch:delegate-subtask
Define the execution contract for isolating a research sub-task — input schema, budget, return summary, evidence list, failure status. Complements decompose-task (which only splits the problem) by giving each split a bounded, auditable execution unit the runtime AI can farm out to a sub-agent or parallel session.
autosearch:experience-compact
Promote recurring patterns from experience/patterns.jsonl into the compact experience.md digest (≤120 lines, read by runtime AI before calling the skill). Triggers on N-events / file-size / user-feedback / session-end. Guards against single-success noise and pollution via promotion thresholds.