rel-ai-investigation

rel-ai-investigation is a skill for Codex from Kyne0328/rel-ai-local-coding-agent. It costs 59 tokens per session (354 once invoked), scanned A, original, Apache-2.0.

A read-only repository investigation guide for answering technical questions with evidence. It covers architecture checks, feasibility studies, dependency and caller tracing, impact analysis, and checking whether work is implemented.

In plain words
What is it for?
Use it to understand how a repository works, trace what depends on a change, measure a bounded behavior, or decide whether a proposed approach is feasible.
Why use it?
It keeps investigations focused on proving a specific claim instead of collecting large amounts of possibly irrelevant code. It also distinguishes observed, verified, inferred, and unresolved conclusions.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to understand how a repository works, trace what depends on a change, measure a bounded behavior, or decide whether a proposed approach is feasible.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kyne0328/rel-ai-local-coding-agent/rel-ai-investigation
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 Kyne0328/rel-ai-local-coding-agent --skill rel-ai-investigation
Clone the repo
git clone --depth 1 https://github.com/Kyne0328/rel-ai-local-coding-agent

Made for: 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 rel-ai-investigation

README.md
[![agentmods](https://agentmods.dev/badge/skills/kyne0328/rel-ai-local-coding-agent/rel-ai-investigation/github.svg)](https://agentmods.dev/skills/kyne0328/rel-ai-local-coding-agent/rel-ai-investigation)
Your own site
<a href="https://agentmods.dev/skills/kyne0328/rel-ai-local-coding-agent/rel-ai-investigation"><img src="https://agentmods.dev/badge/skills/kyne0328/rel-ai-local-coding-agent/rel-ai-investigation/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 rel-ai-investigation

Your own site · 80×15
<a href="https://agentmods.dev/skills/kyne0328/rel-ai-local-coding-agent/rel-ai-investigation"><img src="https://agentmods.dev/badge/skills/kyne0328/rel-ai-local-coding-agent/rel-ai-investigation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 354 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 original 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.00059 $0.00354
Opus 5 $0.00030 $0.00177
Sonnet 5 $0.00012 $0.00071
Haiku 4.5 $0.00006 $0.00035

Measured 11d ago against content hash 971ad5a9a3b6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

rel-ai-investigation 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.

skills/rel-ai-investigation/SKILL.md · 18 lines

What it actually says

Rel.AI Investigation

Reuse the active work_id opened by rel-ai-workflow. Do not call relai_work with action: "begin" when the same objective already has a work session. Use runtime workflow guidance after every Rel.AI call to decide whether another search, read, measurement, or broader boundary is actually useful. workflow.recommendedActions is the default calibration; current evidence and the investigation question determine when proof is sufficient.

  1. State the question and define what would count as sufficient proof before gathering more context.
  2. Escalate evidence in this order: bootstrap -> search/inspect -> targeted reads -> bounded measurement -> broader reads only if required.
  3. Prefer symbol, reference, caller, search, runtime, or package evidence over broad file dumps. Reuse evidence that is still current.
  4. Read only the files and ranges needed to verify the claim. Use bounded one-shot commands for reproducible measurements; never start a managed process for an audit command.
  5. Stop when the required proof exists. More available context is not a reason to continue investigating.
  6. Classify conclusions as observed, verified, inferred, or unresolved. Tie inferences to the evidence that supports them.
  7. This skill does not edit. If implementation is also requested, hand the verified findings to rel-ai-workflow or rel-ai-debugging instead of restarting the investigation.
Files

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.

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. 11d ago First seen · 18 lines · 59 tokens per session scan A 971ad5a9a3b6

Subscribe to this mod's changes

rel-ai-investigation is a skill published in the GitHub repository Kyne0328/rel-ai-local-coding-agent (19 stars, last pushed 6d ago), licensed Apache-2.0. It adds 59 tokens to every session and 354 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

codexless-browser-repair

Diagnose and temporarily repair Codexless Browser compatibility after a Codex, Chrome Skill, or Browser runtime update when Codexless Browser stopped working. Use for current-version Codexless Browser compatibility drift, not ordinary website bugs, general Browser operation, Codexless install/update work, or long-term…

liyana31811/Codexless · 70 tokens

fix-default

A default procedure for handling bug fixes, organised as a three-step scan and a CP process. The input does not explain what the three steps or CP process contain.

devcodex-labs/devcodex · 21 tokens

repair-prevention-assessment

A completion gate for fixes and self-repair work. It creates a machine-checkable assessment that separates evidence a current issue is closed from evidence that the fix will remain effective.

devcodex-labs/devcodex · 75 tokens

diagnosing-bugs

Diagnose bugs with a reproducible red signal, minimized case, ranked hypotheses, and regression test.

MoonTzai/folderbridge-mcp · 25 tokens

conspiracy

Investigate every bug as if it were intentional. Ask who benefits, connect dots from git history and naming, then arrive at the correct technical fix anyway. Use when user types /conspiracy, says "activate conspiracy" or "conspiracy mode".

repowise-dev/modpack · 53 tokens

senior-at-3am

Maximum terse incident-response persona. No pleasantries, no explanation unless asked. Format - what is broken, one-line fix, done. Mild irritation acceptable, never rude. Use when user types /senior-at-3am, says "activate senior-at-3am" or "3am mode".

repowise-dev/modpack · 69 tokens