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/inscico/i-framework/intentnpx skills add InSciCo/i-framework --skill intentgit clone --depth 1 https://github.com/InSciCo/i-frameworkWhat 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.00059 | $0.00546 |
| Opus 5 | $0.00030 | $0.00273 |
| Sonnet 5 | $0.00012 | $0.00109 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
intent 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 yesterday.
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
/intent — Stage 1: capture the "why"
You retire founder–problem risk before any solution talk. Run a guided interview, one question at a time. Stay on the problem, not the solution — if the founder jumps to features, gently redirect to the pain.
Procedure
1. Set up
Create the Product/ folder if it doesn't exist. If Product/intent.md already exists, read it and offer to refine rather than overwrite.
2. Interview (one question at a time)
Draw out, and challenge thin answers on:
- The problem — in plain language, the pain not the product. ("What's broken today?")
- The target user — who has this most acutely? Push back on "everyone"; get to a specific persona.
- Why now — what changed? The tailwind/shift that makes today the moment.
- Why you — founder–problem fit: lived experience, unfair insight, access. What will keep you in the fight when it's hard?
- Status quo — what does the user do about this today? (The real competitor is usually a workaround or "nothing.")
- Evidence of pain — the cheapest test: who have you actually talked to, and what did they say? Aim for 5–10 people in genuine pain. Accept "it's still a hunch" honestly — but name it.
Use AskUserQuestion for genuine forks; use open prompts for narrative answers. Don't fill silence with invented facts — ask.
3. Synthesize Product/intent.md
Write it using the structure from the plugin's templates/intent.md. Read the draft back to the founder for confirmation/correction before finalizing.
4. Evaluate the gate
Set frontmatter gate: passed when all three hold: (1) a crisp problem statement, (2) a named target user, (3) at least one piece of real pain evidence. Otherwise gate: open and clearly list what's missing — but never block the founder from moving on.
5. Hand off
Point to /ideate as the next step (and /iflow if they want the orchestrator to route them).
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.
- yesterday First seen · 35 lines · 59 tokens per session scan A 839ebf1c4f8f
intent is a skill published in the GitHub repository InSciCo/i-framework (4 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 546 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-31.
Other skills, from other repositories
resume-customizer
Director-level / senior PM resume + cover letter toolkit. Generates ATS-optimized documents using verified metrics and company-type strategies. For interview prep, STAR stories, outreach templates, and salary negotiation, see the references/ folder. Personalize references/YOURPROFILE.md first.
apply
Paste a JD to get full analysis + tailored resume + cover letter. Argument: [paste JD text here].
followup
Follow-up cadence tracker. Flags overdue and urgent applications, then drafts the second-touch email or LinkedIn message in your voice. Argument: none, or a company name to follow up on one.
patterns
Analyze the application tracker for what converts and what wastes time. Surfaces score thresholds, winning archetypes, and the blockers driving rejections, then proposes targeting changes. Argument: none.
track-application
Log a new application or check pipeline status. Argument: [company] [role] [status: applied/screening/interview/offer/rejected].
interview
Full interview prep for a specific company. Argument: [company name] [optional: role title].