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/hoavdc/codexkit/codexkit-procurement-rfp-writernpx skills add hoavdc/CodexKit --skill codexkit-procurement-rfp-writergit clone --depth 1 https://github.com/hoavdc/CodexKitWrote 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/hoavdc/codexkit/codexkit-procurement-rfp-writer)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-procurement-rfp-writer"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-procurement-rfp-writer.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.00062 | $0.01207 |
| Opus 5 | $0.00031 | $0.00603 |
| Sonnet 5 | $0.00012 | $0.00241 |
| Haiku 4.5 | $0.00006 | $0.00121 |
Grade A, and why
codexkit-procurement-rfp-writer 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Procurement RFP Writer
When to Use
- When sourcing new vendors, services, or equipment
- When competitive bidding is required by policy
- When replacing an incumbent supplier
- When standardizing procurement documentation
Procedure
Step 1 — Define Scope
- Background and context for the procurement
- Objectives and desired outcomes
- Scope of work or supply (in/out of scope)
- Contract duration and renewal options
- Budget range (if disclosed)
Step 2 — Technical Requirements
- Mandatory requirements (must-have)
- Desirable requirements (nice-to-have)
- Technical specifications or standards
- Integration requirements with existing systems
- SLA expectations (uptime, response time, quality)
Step 3 — Commercial Terms
- Pricing model: fixed, T&M, unit-based, subscription
- Payment terms and milestones
- Warranty and liability provisions
- Insurance requirements
- Termination and exit provisions
Step 4 — Evaluation Methodology
| Criterion | Weight | Scoring |
|---|---|---|
| Technical capability | 35% | Scored 1–5 per requirement |
| Price/commercial | 30% | Lowest-price or best-value formula |
| Experience/references | 15% | Past performance, case studies |
| Sustainability/ESG | 10% | Environmental and social criteria |
| Implementation plan | 10% | Timeline, resources, risk mitigation |
Step 5 — Submission Instructions
- Submission deadline and format
- Questions and clarifications process
- Contact person and communication rules
- Presentation/demo requirements (if any)
- Confidentiality and non-disclosure requirements
Inputs
| Input | Required | Format |
|---|---|---|
| Requirements specification | Yes | Detailed scope document |
| Budget range | Recommended | Currency range |
| Evaluation criteria and weights | Recommended | Matrix |
| Timeline | Yes | Key dates |
Output
## Request for Proposal — [Title]
### 1. Introduction
[Company] invites proposals for [scope] to support [objective].
Contract period: [duration] with [renewal] option.
### 2. Scope of Work
#### In Scope
- [Item 1]
- [Item 2]
#### Out of Scope
- [Item A]
### 3. Technical Requirements
#### Mandatory (M) / Desirable (D)
| # | Requirement | M/D | Response |
|---|-------------|-----|----------|
| 1 | [Requirement] | M | |
| 2 | [Requirement] | M | |
| 3 | [Requirement] | D | |
### 4. Commercial Proposal
Please provide pricing in the following format:
| Item | Unit | Qty | Unit Price | Total |
|------|------|-----|-----------|-------|
| | | | | |
### 5. Evaluation Criteria
| Criterion | Weight |
|-----------|--------|
| Technical capability | 35% |
| Commercial | 30% |
| Experience | 15% |
| Sustainability | 10% |
| Implementation | 10% |
### 6. Timeline
| Milestone | Date |
|-----------|------|
| RFP issued | [Date] |
| Q&A deadline | [Date] |
| Submission deadline | [Date] |
| Evaluation | [Date range] |
| Award notification | [Date] |
### 7. Submission Instructions
- Format: PDF, max [X] pages
- Email to: [contact]
- Subject line: "RFP Response — [Title]"
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.
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 · 170 lines · 62 tokens per session scan A ac72b64e57a0
codexkit-procurement-rfp-writer is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 1,207 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-09-03.
Other skills, from other repositories
architecting-security
安全架构与治理：威胁建模 (STRIDE/PASTA/LINDDUN)、零信任身份架构、IAM/SSO/MFA/PAM、合规框架 (SOC2/PCI/HIPAA/GDPR)、DLP、隐私工程、安全控制设计。Use when designing security architecture, threat modeling new systems, implementing zero-trust identity, designing IAM/SSO/PAM, building compliance evidence chains, or planning privacy-by-design.
bionic-safety-net
Unified survival infrastructure: health, finance, legal safety, circuit breakers, and structural protection against all ruin classes. The last line of defense.
tdd-workflow
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first. Enforces RED-GREEN-REFACTOR cycle with iron-law compliance.
building-agent-systems
AI agent and LLM system engineering reference covering single-agent dev (ReAct, tool calling, plan-execute), multi-agent coordination (swarm, role decomposition, file locking), LLM security (prompt injection, jailbreak defense, output filtering), RAG architecture (chunking, hybrid retrieval, rerank), and prompt…
cultivating-personas
Distills AI agent voice patterns from conversation into a Persona Voice Card v1.0 (self/user/language/register/emojipolicy/flourish only — no judgment-shaped fields), validates schema + content safety + differentiation, and routes contributions through the existing submission portal. Use when the user wants to…
defending-applications
Application security defense knowledge for builders. Covers Web/API/GraphQL hardening (XSS/SQLi/SSRF/IDOR/BOLA/Mass Assignment/deserialization/upload/path traversal), authentication/authorization (OAuth 2.0/OIDC/JWT/Session/Cookie/SAML/SSO), and LLM application security (prompt injection, jailbreak, RAG poisoning…