qual-coding

qual-coding is a skill for Claude Code, Codex from linxule/interpretive-orchestration. It costs 57 tokens per session (1,045 once invoked), scanned A, original, no licence file.

A guided conversation partner for analysing qualitative data such as interview transcripts and field notes. Qualitative coding means marking and interpreting meaningful parts of this data.

In plain words
What is it for?
Use it during early coding to answer questions about the data, or during later coding to review interpretations through visible reasoning.
Why use it?
It helps researchers examine their data carefully without automatically deciding which labels or ideas the data should contain.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it during early coding to answer questions about the data, or during later coding to review interpretations through visible reasoning.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/linxule/interpretive-orchestration/qual-coding
Install

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.

Any agent
npx skills add linxule/interpretive-orchestration --skill qual-coding
Clone the repo
git clone --depth 1 https://github.com/linxule/interpretive-orchestration

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for qual-coding

README.md
[![agentmods](https://agentmods.dev/badge/skills/linxule/interpretive-orchestration/qual-coding/github.svg)](https://agentmods.dev/skills/linxule/interpretive-orchestration/qual-coding)
Your own site
<a href="https://agentmods.dev/skills/linxule/interpretive-orchestration/qual-coding"><img src="https://agentmods.dev/badge/skills/linxule/interpretive-orchestration/qual-coding/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.

agentmods 80×15 button for qual-coding

Your own site · 80×15
<a href="https://agentmods.dev/skills/linxule/interpretive-orchestration/qual-coding"><img src="https://agentmods.dev/badge/skills/linxule/interpretive-orchestration/qual-coding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,045 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00057 $0.01045
Opus 5.5 $0.00023 $0.00418
Sonnet 5.5 $0.00011 $0.00209
Haiku 4.5 $0.00006 $0.00104

Measured 1mo ago against content hash e4a3003479ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

qual-coding 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 1mo 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.

plugin-kimi/.agents/skills/qual-coding/SKILL.md · 165 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

Changes

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.

  1. 1mo ago First seen · 165 lines · 57 tokens per session scan A e4a3003479ac

Subscribe to this mod's changes

qual-coding is a skill published in the GitHub repository linxule/interpretive-orchestration (20 stars, last pushed 3mo ago), with no licence file. It adds 57 tokens to every session and 1,045 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories

draft-related-work

Drafts or rewrites a Related Work / prior work section positioned against actually-retrieved papers — derives the REQUIRED clusters from the paper's own claimed scope (not just whatever was retrieved), clusters prior work into themes, articulates the delta (what this paper adds) per cluster, enforces a per-cluster…

ShaishavMaisuria/research-paper-lifecycle-skills · 205 tokens

find-papers

Searches scholarly literature with zero API keys across DBLP, Crossref, Semantic Scholar, and arXiv. Use when the user wants to find papers, search the literature, list a conference's proceedings (e.g. "all SIGSPATIAL 2025 papers"), survey related work on a topic, look up papers by author/venue/year, get DOIs or…

ShaishavMaisuria/research-paper-lifecycle-skills · 179 tokens

refactor-research-code

Clean research code for public release while preserving reported results. Uses releaseaudit.py to separate safe mechanical cleanup from ask-first behavior risks and identity leaks. Use for release-ready repos, dead experiment branches, config extraction, documented entrypoints, and double-blind code cleanup.

ShaishavMaisuria/research-paper-lifecycle-skills · 60 tokens

verify-citations

Verifies every citation in a BibTeX .bib file against Crossref, DBLP, Semantic Scholar, and arXiv to catch hallucinated, fabricated, or incorrect references before reviewers do. Use when the user says verify citations, check references, validate bibliography, check my .bib, fake or hallucinated citations, retracted…

ShaishavMaisuria/research-paper-lifecycle-skills · 140 tokens

orchestrate-paper

Goal-driven conductor for the whole idea-to-published-paper lifecycle. Takes a research idea plus experiments and a target ("submit to NeurIPS 2026", or "help me pick a venue") and runs a goal->plan->execute->verify->reflect loop. It plans the stages, invokes the right lifecycle skills in order (literature-review…

ShaishavMaisuria/research-paper-lifecycle-skills · 211 tokens

polish-prose

De-AI-ifies and tightens academic prose without changing any technical claim. Use when a researcher says "this sounds like ChatGPT / AI-written", "humanize my paper", "remove the AI words", "too many delves and leverages", "polish my writing", "tighten the prose", "fix my hedging", "too many Moreover/Furthermore"…

ShaishavMaisuria/research-paper-lifecycle-skills · 211 tokens