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 charlieviettq/awesome-agent-skill --skill grad-action-researchgit clone --depth 1 https://github.com/charlieviettq/awesome-agent-skillWrote 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/charlieviettq/awesome-agent-skill/grad-action-research)<a href="https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/grad-action-research"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/grad-action-research/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/charlieviettq/awesome-agent-skill/grad-action-research"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/grad-action-research.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.00100 | $0.01180 |
| Opus 5 | $0.00050 | $0.00590 |
| Sonnet 5 | $0.00020 | $0.00236 |
| Haiku 4.5 | $0.00010 | $0.00118 |
Grade A, and why
"grad-action-research" 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.
This is a copy
94% identical to grad-action-research — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Action Research
Overview
Action research is a cyclical methodology that integrates research with practice improvement. Originating with Kurt Lewin, it follows iterative Plan-Act-Observe-Reflect cycles where practitioners investigate their own context, implement changes, and generate knowledge simultaneously. Participatory Action Research (PAR) extends this by positioning community members as co-researchers, emphasizing democratic knowledge production and social transformation.
When to Use
- Practitioners want to systematically improve their own professional practice
- Research must produce both knowledge and tangible change in a specific context
- Community stakeholders need to be co-researchers, not just subjects
- The problem is situated, practical, and requires iterative solution development
When NOT to Use
- When the researcher is an external observer with no stake in the practice
- When generalizable theory (not local improvement) is the sole goal
- When participants cannot commit to multiple cycles of reflection and action
- When organizational or political constraints prevent implementing changes
Assumptions
IRON LAW: Action research requires DUAL commitment — to generating
knowledge AND to improving practice. Research without action is
conventional research; action without reflection is just practice.
Both halves are non-negotiable.
Key assumptions:
- Knowledge is produced through action and reflection, not detached observation
- Practitioners are knowledgeable agents capable of researching their own practice
- Change and understanding develop iteratively through multiple cycles
- In PAR, those affected by the research have the right to participate in its design and conduct
Methodology
Step 1: Plan
Identify the problem or area for improvement collaboratively. Conduct reconnaissance (fact-finding about the current situation). Develop an action plan based on the diagnosis. In PAR, ensure stakeholders co-design the plan.
What ships with it
1 file 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.
- 9d ago First seen · 110 lines · 100 tokens per session scan A 6374d46da337
"grad-action-research" is a skill published in the GitHub repository charlieviettq/awesome-agent-skill (26 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 1,180 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to grad-action-research, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
examples
Provide Phoenix, LiveView, Ecto, OTP, or Oban examples. Use when asked for sample code, a walkthrough, a proper implementation, or expected workflow output. Pair with domain skills. NOT for debugging, direct changes, best-practice advice, or audits.
intro
Walk through the Elixir/Phoenix plugin commands, workflow, and features in 6 interactive sections. Use when a new user wants to learn what the plugin offers or needs a refresher on available commands.
toolbox-talk-generator
Generate safety toolbox talks for construction crews. Create contextual safety briefings based on weather, work activities, and recent incidents. Support multiple languages.
knowledge-map
Guide-and-script skill for building course knowledge maps. Use it to turn a course topic, syllabus, textbook outline, notes, or teaching materials into a structured framework, key concept explanations, concept dependencies, and optional Markdown / Markmap / Mermaid / OPML / HTML outputs.