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 agentmods add skills/saski/arnesto/fic-researchnpx skills add saski/arnesto --skill fic-researchgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/fic-research)<a href="https://agentmods.dev/skills/saski/arnesto/fic-research"><img src="https://agentmods.dev/badge/skills/saski/arnesto/fic-research.svg" alt="Measured on agentmods" 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.00035 | $0.00240 |
| Opus 5 | $0.00017 | $0.00120 |
| Sonnet 5 | $0.00007 | $0.00048 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
fic-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 5d 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.
What it actually says
FIC Research
Act as a senior engineer documenting what exists today.
Rules
- Describe current state only.
- Do not propose fixes, refactors, or recommendations.
- Include concrete evidence with file references.
Workflow
- Read every file explicitly mentioned by the user.
- Search the codebase for relevant implementation points, related tests, and connected modules.
- Summarize findings by component:
- What it does
- Where it lives
- How it connects to other components
- Record open questions that need follow-up investigation.
Output
When the repository has thoughts/, save to:
thoughts/shared/research/YYYY-MM-DD-topic.md
Recommended structure:
- Summary
- Detailed findings
- Code references
- Architecture notes
- Open questions
Completion
End with:
- Report path
- 2-4 key findings
- Suggested next step (
fic-create-planwhen planning is requested)
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.
- 5d ago First seen · 47 lines · 35 tokens per session scan A 0f9917a0f861
fic-research is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed 9d ago), licensed Unlicense. It adds 35 tokens to every session and 240 once invoked, about $0.0002 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-31.
Other skills, from other repositories
pixir-delegate
Use Pixir as a headless subagent runtime from Claude Code or any harness with skill ! preprocessing (Codex roots and other no-hydration hosts use pixir-delegate-codex instead) — one-shot workers (pixir --json), parallel fan-out to N children (pixir delegate --spec), resumable steering (pixir resume), evidence…
pixir-delegate-codex
Use when a Codex CLI/Desktop root should fan out subagents, delegate to Pixir workers, run parallel workers, or manage a resident delegation daemon via Pixir Delegate; covers Codex preflight, AGENTS.md, approvals/sandbox, dry-run, daemon start/status/attach/cancel, closure evidence, and audited single-run execution…
pixir-diagnostics
Diagnose Pixir and T3 Code Pixir incidents from local canonical evidence. Use when a Pixir run, ACP/T3 thread, subagent/workflow, provider replay, or daily-driver dogfood session appears stuck, inconsistent, missing tool output, or hard to classify.
readonly-review
Run a no-network read-only review practice with two explorer steps and one synthesis step.
pixir-delegate-native
Delegate work to subagents from INSIDE a Pixir session using the native Subagent tools (spawnagent, waitagent, closeagent, listagents, sendinput) instead of shelling out to the pixir CLI. Use when you are a Pixir session that needs to fan out parallel workers, steer a child, or run skill-backed workflow templates …
repo-contracts-and-boundaries
Use when turning architecture, layering, ownership, dependency direction, schemas, structural metrics, quality thresholds, baselines, allowlists, or generated quality snapshots into repository checks.