Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add qte77/claude-code-plugins/plugin install cc-metaWrote 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/qte77/claude-code-plugins/cross-checking-research)<a href="https://agentmods.dev/skills/qte77/claude-code-plugins/cross-checking-research"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/cross-checking-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/qte77/claude-code-plugins/cross-checking-research"><img src="https://agentmods.dev/badge/skills/qte77/claude-code-plugins/cross-checking-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.00050 | $0.00845 |
| Opus 5.5 | $0.00020 | $0.00338 |
| Sonnet 5.5 | $0.00010 | $0.00169 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
cross-checking-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 21d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Cross-Check
Target: $ARGUMENTS
Bidirectional cross-check between a consumer repo (a project with ADRs, plans, findings) and a research hub (a catalog of concepts, tools, and per-repo learnings):
- Pull — hub concepts/tools/sources the consumer has not yet cited or applied, each mapped to the consumer file (ADR or plan) that should cite or adopt it.
- Push — the consumer's reusable findings the hub does not yet capture, with the top ones drafted in the hub's per-repo-learnings format, ready to PR.
Arguments
| Position | Name | Required | Default | Description |
|---|---|---|---|---|
| 1 | consumer-repo-path |
yes | — | Absolute path to the consumer repo. |
| 2 | research-hub-path |
yes* | — | Absolute path to the hub. *Ask the user if not given; do not guess. |
| 3 | focus |
no | — | Narrows the cross-check to a topic (e.g. evaluation, governance). |
When NOT to use
- The consumer has no decisions/findings yet (nothing to push, nothing to map pulls onto).
- You only need a literature search — use a research skill instead.
Workflow
-
Resolve paths. Confirm both directories exist and are readable. The hub should contain an index/README and a per-repo learnings dir (e.g.
docs/learnings/per-repo/); if its layout differs, tell the user rather than guessing receptacles. -
Run the bundled workflow (the instruction to call Workflow is the opt-in):
Workflow({ scriptPath: "${CLAUDE_PLUGIN_ROOT}/workflows/research-cross-check.js", args: { consumer: "<abs path>", research: "<abs path>", focus: "<optional>" } })argsreaches the script as a JSON string; it is parsed there. Phases: Scan (read both repos in parallel) → Diff (pull + push candidates) → Draft (top 4 push items). All agents are read-only; nothing is written to either repo. -
Fallback when the Workflow tool is unavailable: do the same three phases inline — read the consumer's
docs/decisions/,docs/plans/, AGENTS/README/CHANGELOG; read the hub's index and the landscape docs matching the consumer's domain; list pulls and pushes; draft the top items.
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.
- 21d ago First seen · 70 lines · 50 tokens per session scan A f14b880ac104
cross-checking-research is a skill published in the GitHub repository qte77/claude-code-plugins (3 stars, last pushed 4d ago), licensed Apache-2.0. It adds 50 tokens to every session and 845 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-09-26.
Other skills, from other repositories
android-kotlin-compose
Android development with Kotlin and Jetpack Compose. Use when user mentions "Compose", "Jetpack Compose", "Material3", "Hilt", "Room", "ViewModel", or needs to build Android UI, implement MVVM architecture, manage Compose state, or integrate Jetpack libraries (Navigation, Room, Hilt, ViewModel). Triggers on…
android-kotlin-coroutines
Android development with Kotlin Coroutines and Flow. Use when user mentions "coroutines", "suspend", "Flow", "StateFlow", "SharedFlow", "viewModelScope", "lifecycleScope", or needs to implement async programming, handle structured concurrency, integrate coroutines with Retrofit/Room/WorkManager, or write coroutine…
codex-advisor
Advisory consultation skill for architectural reviews, design decisions, code analysis, and technology evaluation. Codex provides recommendations without making code changes. Invoked by phrases like "consult Codex", "get Codex's opinion", "ask Codex about", "have Codex review", "Codex analysis", "validate this…
ast-grep
Structural code search and rewriting using AST patterns. Use when user mentions "ast-grep", "sg", or needs to search codebases using Abstract Syntax Tree patterns, find specific code structures, perform complex queries beyond text search, or rewrite code at scale. Triggers on requests for pattern matching, code…
github-cli
This skill should be used when working with GitHub CLI (gh) for repository management, pull requests, issues, API access, GitHub Actions, or automation workflows. Provides comprehensive guidance on gh command patterns, security considerations, and best practices.
android-analysis
Expert Android and Java reverse engineering for APK/AAR/JAR decompilation and inspection. Use when user mentions "decompile", "jadx", "apktool", "reverse engineer", or needs to analyze Android binaries, unpack libraries, understand obfuscated apps, or extract resources from compiled artifacts.