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 gpsaggese/helpers --skill research_idea.update_readmegit clone --depth 1 https://github.com/gpsaggese/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/gpsaggese/helpers/research_idea.update_readme)<a href="https://agentmods.dev/skills/gpsaggese/helpers/research_idea.update_readme"><img src="https://agentmods.dev/badge/skills/gpsaggese/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/gpsaggese/helpers/research_idea.update_readme"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/research_idea.update_readme.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.00012 | $0.00405 |
| Opus 5.5 | $0.00005 | $0.00162 |
| Sonnet 5.5 | $0.00002 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00040 |
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 yesterday.
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
<TIMESTAMP>from the comment at the end ofresearch/ideas/README.md, e.g.// Last update timestamp: "Aug 3 10:54" - Find every
research/ideas/*.mdfile modified or added after<TIMESTAMP>, or with no row in the table yet - Build the list of those files,
<FILES>
Read the Template
- Read
.claude/templates/research_idea.template.mdto learn 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 from the file content and status prefix, as well as you can
- Sort all rows by descending
Specs Complete
Update the Timestamp
- Set 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 of files in
<FILES>. Re-sorting the table is the only change allowed to other rows - 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.
- yesterday First seen · 46 lines · 12 tokens per session scan A 6a60e8b8abb3
research_idea.update_readme is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 12 tokens to every session and 405 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-11-06.
research_idea.update_readme compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| research_idea.update_readmegpsaggese/helpers | Skill | 158 | today | Apache-2.0 | A | 12 | Claude Code |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | today | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 99k | today | Apache-2.0 | A | 19 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| chat-pet-sprite-creationmicrosoft/vscode | Skill | 195k | today | MIT | A | 53 | Claude Code, Codex |