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 BingHanOfUESTC/open_agent_team --skill research-lineage-mappergit clone --depth 1 https://github.com/BingHanOfUESTC/open_agent_teamWrote 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/binghanofuestc/open_agent_team/research-lineage-mapper)<a href="https://agentmods.dev/skills/binghanofuestc/open_agent_team/research-lineage-mapper"><img src="https://agentmods.dev/badge/skills/binghanofuestc/open_agent_team/research-lineage-mapper/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/binghanofuestc/open_agent_team/research-lineage-mapper"><img src="https://agentmods.dev/badge/skills/binghanofuestc/open_agent_team/research-lineage-mapper.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.00047 | $0.00382 |
| Opus 5 | $0.00023 | $0.00191 |
| Sonnet 5 | $0.00009 | $0.00076 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
research-lineage-mapper 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 7d 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
Research Lineage Mapper
This local skill turns paper collections into a research trajectory.
Core Questions
For any direction, answer:
What problem was originally defined?
Which papers changed the problem definition?
Which methods became dominant?
Which labs or teams repeatedly contributed?
Which benchmarks shaped progress?
Which assumptions remain fragile?
What is still unsolved?
Where is the direction likely to go?
Mapping Axes
Use at least four axes:
Time: early work -> transition -> current frontier
Problem: task definition -> objective -> evaluation
Method: algorithm/model/data/training/inference route
People: labs, PIs, students, companies, open-source communities
Report Artifacts
# Research Lineage Map
## Timeline
| Period | Key Question | Representative Papers | Main Shift |
|---|---|---|---|
## Problem-Method Matrix
| Problem Definition | Method Family | Representative Papers | Strength | Limitation |
|---|---|---|---|---|
## Lab And People Map
| Lab/Team | Key People | Representative Contributions | Evidence |
|---|---|---|---|
## Benchmark Evolution
| Benchmark/Data | What It Measures | What It Misses | Related Papers |
|---|---|---|---|
## Open Problems
## Future Directions
Hard Rules
- Do not invent advisor/student relationships.
- Mark inferred relationships as inference.
- Do not overstate impact from a single paper.
- Distinguish influential, representative, recent, and speculative papers.
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.
- 7d ago First seen · 68 lines · 47 tokens per session scan A 4211730688b3
research-lineage-mapper is a skill published in the GitHub repository BingHanOfUESTC/open_agent_team (106 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 382 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-09-03.
Other skills, from other repositories
company-product-context
Compiles comprehensive company product context from PDF documents, web research, and industry knowledge.
python-lib-analyzer
Analyze any Python library structure, explore modules, classes, and functions with signatures and documentation.
Ability Generator
This skill generates markdown skill templates to be later used.
nexus-configuration
A skill for reading, planning, approving, and checking configuration in Nexus, the current private conversation or room. It covers settings such as agents, rooms, providers, channels, connectors, skills, models, tools, and MCP connections.
agentica
How to answer questions about the agentica product you are running inside — CLI flags, config.yaml profiles, API keys, models, sessions, resume, workspace, AGENTS.md standing rules, skills, logs, upgrade, and selfmanage. Use when asked how agentica works, how to configure or upgrade it, where state lives on disk…
generate-ai-rules
Generate AI assistant configuration files for a repository — CLAUDE.md, AGENTS.md, and Cursor rules (.cursor/rules/.mdc) — from codebase analysis. Use whenever the user wants to create or update CLAUDE.md, AGENTS.md, agent rules, Cursor rules, AI coding assistant configuration, or "onboard AI tools" to a project, even…