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 agentmods add skills/nimblebraininc/upjack/research-methodologynpx skills add NimbleBrainInc/upjack --skill research-methodologygit clone --depth 1 https://github.com/NimbleBrainInc/upjackWrote 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/nimblebraininc/upjack/research-methodology)<a href="https://agentmods.dev/skills/nimblebraininc/upjack/research-methodology"><img src="https://agentmods.dev/badge/skills/nimblebraininc/upjack/research-methodology.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00431 |
| Opus 5 | $0.00000 | $0.00216 |
| Sonnet 5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
research-methodology 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 5d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Methodology
Systematic approach to investigating topics, evaluating sources, and synthesizing findings.
When to Use
- A new topic is created
- Daily topic monitoring (triggered via schedule)
- User asks to research a topic or find sources
Research Process
1. Topic Scoping
Before searching, understand what you're looking for:
- Read the topic's
key_questionsfor specific angles - Check existing sources and notes to avoid duplication
- Identify gaps in current coverage
2. Source Discovery
Use platform:web_search with targeted queries:
- Start broad, then narrow based on initial findings
- Search for: academic papers, industry reports, expert blogs, news articles
- Try multiple query formulations for comprehensive coverage
3. Source Evaluation
For each potential source:
- Assess credibility (1-5 scale per context.md guidelines)
- Check publication date for recency
- Note author credentials and potential bias
- Create a source entity with full metadata
4. Note Extraction
Use platform:web_scrape or platform:pdf_extract to read sources:
- Create one note per distinct insight
- Tag with appropriate
claim_type - Include direct quotes for key claims
- Link note to both source and topic via relationships
5. Synthesis
When the user asks for a report or when sufficient notes exist:
- Group notes by theme, not by source
- Identify consensus and conflicts across sources
- Highlight the strongest evidence
- Note gaps and limitations
Daily Monitoring
For the daily schedule:
- List all active topics
- For each topic, search for new developments (past 24 hours)
- If significant new information found:
- Create source and note entities
- Add "new-development" tag
- Skip topics tagged "paused" or with status "archived"
Rules
- Minimum 3 sources before generating a report
- Always include source credibility in reports
- Flag when multiple sources contradict each other
- Never present a single source's claim as established fact
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.
- 5d ago First seen · 67 lines · 0 tokens per session scan A 159ca9dc1c0c
research-methodology is a skill published in the GitHub repository NimbleBrainInc/upjack (9 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 431 tokens. 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
playwright
Use when the task requires capturing or automating a real browser from the terminal.
caveman
用最原始的方式思考问题，剥离一切抽象，直击本质。当用户需要从零开始思考、被抽象搞晕了、或想要最根本的解释时使用。.
frontmcp-guides
Tutorials, end-to-end walkthroughs, and complete reference projects for FrontMCP. Use when you want a getting-started guide, a full worked example, or to learn best practices by following a step-by-step build rather than a single API reference. Includes a beginner weather-API server (tool plus static resource, Zod…
create-skill
Create instruction-only skills that package knowledge and workflow guides for AI clients.
yalc-orientation
First-touch onboarding for someone who just opened the YALC repo. Triggers when the user pastes the repo URL https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system (with or without trailing slash, with or without .git), or says any of: 'what is yalc', 'what is this', "let's start", "let's go", 'i just cloned…
book-technical
Technical book patterns — concept progression gradient, code block rules, diagrams, API reference format, lab design.