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 Immortalqx/my_codex_skills --skill phd-vibe-research-workflowgit clone --depth 1 https://github.com/Immortalqx/my_codex_skillsWrote 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/immortalqx/my_codex_skills/phd-vibe-research-workflow)<a href="https://agentmods.dev/skills/immortalqx/my_codex_skills/phd-vibe-research-workflow"><img src="https://agentmods.dev/badge/skills/immortalqx/my_codex_skills/phd-vibe-research-workflow/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/immortalqx/my_codex_skills/phd-vibe-research-workflow"><img src="https://agentmods.dev/badge/skills/immortalqx/my_codex_skills/phd-vibe-research-workflow.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.00118 | $0.01376 |
| Opus 5 | $0.00059 | $0.00688 |
| Sonnet 5 | $0.00024 | $0.00275 |
| Haiku 4.5 | $0.00012 | $0.00138 |
Grade A, and why
phd-vibe-research-workflow 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 11d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe Research Workflow
Overview
Vibe Research is the modern research workflow where large language models and AI coding tools handle mechanical tasks (implementation, figure rendering, language polish) while the researcher retains full ownership of research direction, problem framing, experimental design, and factual accuracy. The goal is a two-to-five times productivity gain on routine tasks without compromising academic integrity.
The skill has three sub-flows: Vibe Coding (AI-assisted code), Vibe Figure (AI-assisted figure production), Vibe Writing (AI-assisted prose polish). Each is governed by six behavioural rules that draw a hard line between acceptable use (mechanical acceleration, auxiliary suggestions, style correction) and academic misconduct (fabricated citations, outsourced scientific judgment, hidden AI authorship).
This skill is a meta-skill that orchestrates tool selection, flow design, and integrity enforcement across a research session. It consolidates the the curriculum's Vibe Research section into a single invocable procedure.
When to use this skill
- Starting a new AI-assisted work block (a morning of coding, a figure day, a writing session).
- The user asks 'how to use AI for research', 'Vibe Coding tips', 'AI-assisted writing workflow', 'which AI tool for this'.
- The user is choosing between Cursor, Claude Code, Codex, Figma, Gemini, or other tools.
- The user wants a workflow plan for a multi-day project involving AI.
- The user suspects AI output has drifted into unacceptable territory (fabricated citations, outsourced reasoning).
When NOT to use this skill
- The user wants AI to generate the paper directly. Reject politely; the integrity rules forbid it. Redirect to
phd-intro-drafter,phd-tech-paper-template, orphd-pre-submission-reviewerdepending on intent. - The user wants a code implementation done. This skill guides the process; it does not replace the implementation itself.
- The user wants to evaluate research direction. Use
phd-idea-evaluator(seephd-idea-evaluatorand its reference files for deeper disruptive-innovation evaluation).
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 116 lines · 118 tokens per session scan A f0e21ccbcee1
phd-vibe-research-workflow is a skill published in the GitHub repository Immortalqx/my_codex_skills (52 stars, last pushed 1mo ago), licensed MIT. It adds 118 tokens to every session and 1,376 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…