Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBnpx agentmods add skills/davidroliverba/architectkb/score-rfiWrote 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/davidroliverba/architectkb/score-rfi)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/score-rfi"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/score-rfi/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/davidroliverba/architectkb/score-rfi"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/score-rfi.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.00015 | $0.01991 |
| Opus 5 | $0.00008 | $0.00996 |
| Sonnet 5 | $0.00003 | $0.00398 |
| Haiku 4.5 | $0.00002 | $0.00199 |
Grade A, and why
score-rfi 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 9d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/score-rfi
Score vendor RFI responses stored in SQLite databases using a standardised 0-3 rubric.
Usage
/score-rfi <vendor-name>
/score-rfi pwc
/score-rfi accenture
/score-rfi ibm
Prerequisites
Before scoring, ensure the vendor's CSV has been converted to SQLite:
# Convert CSV to SQLite (see /csv-to-sql skill)
node scripts/csv-to-sqlite.js "Inbox/<vendor>-rfi-responses.csv" --start-row <n> --fts --verbose
Scoring Rubric (0-3 Scale)
| Score | Rating | Qualitative Assessment |
|---|---|---|
| 3 | High | Strong proven experience; clear, detailed answer demonstrating deep understanding; high confidence in capability |
| 2 | Medium | Some capability demonstrated; potential but unproven or limited evidence; moderate risk |
| 1 | Low | Insufficient evidence; generic or superficial response; does not address specifics; high risk |
| 0 | Zero | Not demonstrated at all; no evidence or response; very high risk |
Scoring Criteria
When evaluating responses, consider:
- Domain Specificity - Does the response demonstrate understanding of your industry operations and relevant regulations?
- Organisation Context - Does it show awareness of your organisation's scale, operations, existing systems?
- Technical Depth - Are specific technologies, frameworks, methodologies named with concrete examples?
- Proven Experience - Are past implementations cited? Client references? Metrics?
- Risk Indicators - Are there red flags like "we will learn", "to be determined", "partner with"?
Score Format
All scores MUST be written in this format:
[score] - [brief reason for score]
Examples:
3 - Strong domain-specific response with mature frameworks; explicit regulatory references; relevant experience cited2 - Solid methodology but no domain-specific examples; generic enterprise approach1 - Insufficient evidence of capability; significant capability gap0 - No response provided
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.
- 9d ago First seen · 262 lines · 15 tokens per session scan A 4a3381fd9c24
score-rfi is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It adds 15 tokens to every session and 1,991 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.