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 skills add jdmorag97-rgb/DDC_Skills_for_AI_Agents_in_Construction --skill material-procurement-trackergit clone --depth 1 https://github.com/jdmorag97-rgb/DDC_Skills_for_AI_Agents_in_ConstructionWrote 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/jdmorag97-rgb/ddc_skills_for_ai_agents_in_construction/material-procurement-tracker)<a href="https://agentmods.dev/skills/jdmorag97-rgb/ddc_skills_for_ai_agents_in_construction/material-procurement-tracker"><img src="https://agentmods.dev/badge/skills/jdmorag97-rgb/ddc_skills_for_ai_agents_in_construction/material-procurement-tracker/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/jdmorag97-rgb/ddc_skills_for_ai_agents_in_construction/material-procurement-tracker"><img src="https://agentmods.dev/badge/skills/jdmorag97-rgb/ddc_skills_for_ai_agents_in_construction/material-procurement-tracker.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.00025 | $0.01369 |
| Opus 5 | $0.00013 | $0.00685 |
| Sonnet 5 | $0.00005 | $0.00274 |
| Haiku 4.5 | $0.00003 | $0.00137 |
Grade A, and why
material-procurement-tracker 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.
This is a copy
100% identical to material-procurement-tracker — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Material Procurement Tracker
Business Case
Long lead items and material procurement require careful tracking to avoid schedule delays.
Technical Implementation
import pandas as pd
from datetime import date, timedelta
from typing import Dict, Any, List, Optional
from dataclasses import dataclass, field
from enum import Enum
class ProcurementStatus(Enum):
REQUISITIONED = "requisitioned"
RFQ_SENT = "rfq_sent"
QUOTED = "quoted"
PO_ISSUED = "po_issued"
IN_PRODUCTION = "in_production"
SHIPPED = "shipped"
DELIVERED = "delivered"
class Priority(Enum):
CRITICAL = "critical"
HIGH = "high"
NORMAL = "normal"
LOW = "low"
@dataclass
class ProcurementItem:
item_id: str
description: str
spec_section: str
quantity: float
unit: str
required_date: date
lead_time_days: int
status: ProcurementStatus
priority: Priority
vendor: str = ""
po_number: str = ""
po_amount: float = 0.0
order_date: Optional[date] = None
expected_delivery: Optional[date] = None
actual_delivery: Optional[date] = None
@property
def must_order_by(self) -> date:
return self.required_date - timedelta(days=self.lead_time_days)
@property
def is_late_to_order(self) -> bool:
if self.status in [ProcurementStatus.PO_ISSUED, ProcurementStatus.IN_PRODUCTION,
ProcurementStatus.SHIPPED, ProcurementStatus.DELIVERED]:
return False
return date.today() > self.must_order_by
class MaterialProcurementTracker:
def __init__(self, project_name: str):
self.project_name = project_name
self.items: Dict[str, ProcurementItem] = {}
self._counter = 0
def add_item(self, description: str, spec_section: str, quantity: float,
unit: str, required_date: date, lead_time_days: int,
priority: Priority = Priority.NORMAL) -> ProcurementItem:
self._counter += 1
item_id = f"PROC-{self._counter:04d}"
item = ProcurementItem(
item_id=item_id,
description=description,
spec_section=spec_section,
quantity=quantity,
unit=unit,
required_date=required_date,
lead_time_days=lead_time_days,
status=ProcurementStatus.REQUISITIONED,
priority=priority
)
self.items[item_id] = item
return item
def issue_po(self, item_id: str, vendor: str, po_number: str,
amount: float, expected_delivery: date):
if item_id in self.items:
item = self.items[item_id]
item.status = ProcurementStatus.PO_ISSUED
item.vendor = vendor
item.po_number = po_number
item.po_amount = amount
item.order_date = date.today()
item.expected_delivery = expected_delivery
def update_status(self, item_id: str, status: ProcurementStatus):
if item_id in self.items:
self.items[item_id].status = status
if status == ProcurementStatus.DELIVERED:
self.items[item_id].actual_delivery = date.today()
def get_items_to_order(self) -> List[ProcurementItem]:
"""Get items that need to be ordered soon."""
cutoff = date.today() + timedelta(days=14)
return [i for i in self.items.values()
if i.status in [ProcurementStatus.REQUISITIONED, ProcurementStatus.RFQ_SENT,
ProcurementStatus.QUOTED]
and i.must_order_by <= cutoff]
def get_late_items(self) -> List[ProcurementItem]:
return [i for i in self.items.values() if i.is_late_to_order]
def get_summary(self) -> Dict[str, Any]:
by_status = {}
total_value = 0
for item in self.items.values():
status = item.status.value
by_status[status] = by_status.get(status, 0) + 1
total_value += item.po_amount
return {
'total_items': len(self.items),
'by_status': by_status,
'total_po_value': total_value,
'items_to_order': len(self.get_items_to_order()),
'late_items': len(self.get_late_items())
}
def export_log(self, output_path: str):
data = [{
'ID': i.item_id,
'Description': i.description,
'Spec': i.spec_section,
'Qty': i.quantity,
'Unit': i.unit,
'Required': i.required_date,
'Lead Time': i.lead_time_days,
'Must Order By': i.must_order_by,
'Status': i.status.value,
'Vendor': i.vendor,
'PO': i.po_number,
'Amount': i.po_amount
} for i in self.items.values()]
pd.DataFrame(data).to_excel(output_path, index=False)
What ships with it
2 files 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.
- 9d ago First seen · 182 lines · 25 tokens per session scan A 2489694e7be8
material-procurement-tracker is a skill published in the GitHub repository jdmorag97-rgb/DDC_Skills_for_AI_Agents_in_Construction (2 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 1,369 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to material-procurement-tracker, differing in 0 lines, and is treated as a copy.
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.