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 HaowenHou/AgenticResearchWiki --skill project-doc-updategit clone --depth 1 https://github.com/HaowenHou/AgenticResearchWikiWrote 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/haowenhou/agenticresearchwiki/project-doc-update)<a href="https://agentmods.dev/skills/haowenhou/agenticresearchwiki/project-doc-update"><img src="https://agentmods.dev/badge/skills/haowenhou/agenticresearchwiki/project-doc-update/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/haowenhou/agenticresearchwiki/project-doc-update"><img src="https://agentmods.dev/badge/skills/haowenhou/agenticresearchwiki/project-doc-update.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.00034 | $0.01158 |
| Opus 5 | $0.00017 | $0.00579 |
| Sonnet 5 | $0.00007 | $0.00232 |
| Haiku 4.5 | $0.00003 | $0.00116 |
Grade A, and why
project-doc-update 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc organization
Experimental side tracks
If a new technical track affects multiple links among data / training / eval, add a corresponding doc under ExperimentalTracks/, named YYMMDD-track-name.md, and add a link to it in Overview.md.
Shared techniques
If a technique is used by multiple links among data / training / eval, put it under Shared/, named YYMMDD(optional)-tech-name.md, and link to it from each link's relevant doc.
Storyline
The project's main narrative (background, related work, goals) lives under Storyline/, as Introduction.md / RelatedWork.md / Target.md. Overview.md links to these at the top; keep them consistent when editing.
Research notes
Research, comparisons, and decision-rationale docs go under ResearchNotes/, split by topic into subdirectories: Data/ Models/ Training/ Eval/ Benchmarks/ RelatedPapers/. When adding a research note, place the file in the right subdirectory and add a wiki link to it in the index at ResearchNotes/ResearchNotesOverview.md.
Common directories
- If a dataset's description, special processing, or filtering rules grow too large, create a subdirectory under
Data/on demand (e.g.Data/Datasets/<dataset name>/). Each such subdirectory needs an entry doc that links to the rest. - Same applies to training, eval, and other directories.
Flexibility
- Because research is so varied, no single doc-organization scheme fits every situation. Instead of enumerating every case, the organization should satisfy a few overall rules:
-
Track classification (a) Experimental techniques that span multiple links →
ExperimentalTracks/. (b) Experimental techniques scoped to a single link → create a doc or subdirectory under that link. -
Single doc vs. subdirectory Pick "single doc" vs. "subdirectory with multiple docs" mainly by content length.
-
Entry docs and linking rules (a) Every subdirectory must contain an entry doc that links to the rest of its contents. (b) Whether you create a doc or a subdirectory, there must be a link pointing to the new doc / subdirectory's entry.
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 · 65 lines · 34 tokens per session scan A 55b15c14da5a
project-doc-update is a skill published in the GitHub repository HaowenHou/AgenticResearchWiki (29 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 1,158 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-30.
Other skills, from other repositories
autogpt-agents
Autonomous AI agent platform for building and deploying continuous agents. Use when creating visual workflow agents, deploying persistent autonomous agents, or building complex multi-step AI automation systems.
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.