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 causify-ai/helpers --skill research_idea.update_readmegit clone --depth 1 https://github.com/causify-ai/helpersWrote 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/causify-ai/helpers/research_idea.update_readme)<a href="https://agentmods.dev/skills/causify-ai/helpers/research_idea.update_readme"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/research_idea.update_readme/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/causify-ai/helpers/research_idea.update_readme"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/research_idea.update_readme.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 3 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00012 | $0.00416 |
| Opus 5.5 | $0.00005 | $0.00166 |
| Sonnet 5.5 | $0.00002 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
research_idea.update_readme 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 1mo 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
Goal
- Update
research/ideas/README.mdto reflect the current content ofresearch/ideas/*.md
Workflow
Find the Files to Process
- Extract the timestamp
<TIMESTAMP>from the comment at the end ofresearch/ideas/README.md, e.g.// Last update timestamp: "Aug 3 10:54" - Find every file in
research/ideas/*.mdmodified or added after<TIMESTAMP>, or not yet present as a row in the table - Build the list of files to process,
<FILES>
Read the Template
- Read
.claude/templates/research_idea.template.mdto know what each idea file should contain
Update the Table
- For each file in
<FILES>, add or update its row inresearch/ideas/README.mdusing the column order:| File | Links | Status | Assignee | Specs Complete | GitHub Issue | Result | - Fill each column to the best of your ability from the file's content and status prefix
- Sort all rows by descending
Specs Complete
Update the Timestamp
- Update the
// Last update timestamp: "..."comment at the end of the file to the current timestamp
Conventions
- Follow
.claude/skills/research_idea.rules.md
Constraints
- Only touch rows for files in
<FILES>; do not rewrite rows for unchanged files beyond re-sorting the table - Do not remove a row for a file that still exists in
research/ideas/*.md
Verification
- Every file in
<FILES>has a row in the table - Rows are sorted by descending
Specs Complete - The
// Last update timestamp: "..."comment reflects the current time
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.
- 1mo ago Changed 000fda030212
- 1mo ago First seen · 47 lines · 12 tokens per session scan A 517f748bbc06
research_idea.update_readme is a skill published in the GitHub repository causify-ai/helpers (150 stars, last pushed yesterday), licensed Apache-2.0. It adds 12 tokens to every session and 416 once invoked, about $0.0000 per session on Opus 5.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
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…