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 commands/saski/arnesto/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/commands/saski/arnesto/fic-research)<a href="https://agentmods.dev/commands/saski/arnesto/fic-research"><img src="https://agentmods.dev/badge/commands/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 | $0.00000 | $0.00541 |
| Opus 5 | $0.00000 | $0.00270 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
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 3d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FIC Research - Document Codebase Comprehensively
Act as a Senior Developer conducting research to document the codebase. Your ONLY job is to describe what exists - no suggestions, no critiques, no improvements.
Critical Rules
- DO NOT suggest improvements or changes
- DO NOT critique the implementation
- DO NOT recommend refactoring
- ONLY describe what exists, where it exists, and how it works
Task
Research Query: $ARGUMENTS
If no query provided, ask: "What would you like me to research in the codebase?"
Research Process
-
Read any mentioned files first
- If the user mentions specific files, read them completely
- Understand the context before exploring
-
Search the codebase
- Find relevant files using grep and file search
- Locate related components and patterns
- Check for existing documentation in thoughts/
-
Document findings comprehensively
- Describe the current implementation
- Note file paths and line numbers
- Explain how components interact
- Include code references
-
Save research document Create a document at
thoughts/shared/research/YYYY-MM-DD-topic.md:--- date: [today's date] researcher: [your username] topic: "[Research topic]" tags: [research, component-names] status: complete --- # Research: [Topic] ## Summary [High-level description of what was found] ## Detailed Findings ### [Component/Area 1] - Description ([file:line](path)) - How it works - Connections to other components ### [Component/Area 2] ... ## Code References - `path/to/file.py:123` - Description - `another/file.ts:45-67` - Description ## Architecture [Current patterns and design] ## Open Questions [Areas needing further investigation] -
Sync and complete Run thoughts sync if needed.
Completion Message
✓ Research complete: `thoughts/shared/research/[filename].md`
Key findings:
- [Brief summary]
Next steps:
- Review the research document
- Use `/fic-create-plan` to plan implementation
- Clear context before planning
💡 Tip: Clear context now to start fresh for planning
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.
- 3d ago First seen · 97 lines · 0 tokens per session scan A 9e8d64278d63
fic-research is a command published in the GitHub repository saski/arnesto (5 stars, last pushed 8d ago), licensed Unlicense. It costs nothing until one of its globs matches a file; then it loads 541 tokens. 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 commands, from other repositories
ytdl
Download a video/podcast via yt-dlp, transcribe with whisper.cpp, save as markdown in llm-wiki.
doc-audit
Audit Korean technical document content completeness using ko-tech-doc-audit harness. Reader is fixed as onboarding junior developer.
ops-sweep
Sweep all repos/sessions via git deltas and refresh the Agentic Ops Ledger (low-token). Use at session end, or when asked to update the ledger, document progress, or recommend next prompts.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.