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 contractor-matching-aigit 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/contractor-matching-ai)<a href="https://agentmods.dev/skills/jdmorag97-rgb/ddc_skills_for_ai_agents_in_construction/contractor-matching-ai"><img src="https://agentmods.dev/badge/skills/jdmorag97-rgb/ddc_skills_for_ai_agents_in_construction/contractor-matching-ai/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/contractor-matching-ai"><img src="https://agentmods.dev/badge/skills/jdmorag97-rgb/ddc_skills_for_ai_agents_in_construction/contractor-matching-ai.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.00033 | $0.05841 |
| Opus 5 | $0.00016 | $0.02920 |
| Sonnet 5 | $0.00007 | $0.01168 |
| Haiku 4.5 | $0.00003 | $0.00584 |
Grade A, and why
contractor-matching-ai 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 8d 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 contractor-matching-ai — 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 — 742 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Contractor Matching
Overview
This skill implements AI-powered contractor matching for construction projects. Analyze project requirements against contractor capabilities, track historical performance, and generate recommendations based on multiple criteria.
Matching Criteria:
- Technical capabilities & expertise
- Past performance scores
- Certifications & licenses
- Geographic availability
- Capacity & current workload
- Pricing competitiveness
- Safety records
Quick Start
from dataclasses import dataclass, field
from typing import List, Dict, Optional
from datetime import date
import numpy as np
@dataclass
class Contractor:
contractor_id: str
name: str
specializations: List[str]
certifications: List[str]
performance_score: float # 0-100
safety_score: float # 0-100
regions: List[str]
capacity_available: float # 0-100 percentage
avg_bid_variance: float # % above/below average
@dataclass
class ProjectRequirement:
project_id: str
work_types: List[str]
required_certs: List[str]
region: str
estimated_value: float
priority: str # cost, quality, speed, safety
def match_contractors(project: ProjectRequirement,
contractors: List[Contractor],
top_n: int = 5) -> List[Dict]:
"""Simple contractor matching"""
scores = []
for c in contractors:
# Check basic eligibility
if project.region not in c.regions:
continue
work_match = len(set(project.work_types) & set(c.specializations))
if work_match == 0:
continue
cert_match = len(set(project.required_certs) & set(c.certifications))
if cert_match < len(project.required_certs):
continue
# Calculate score based on priority
if project.priority == 'quality':
score = c.performance_score * 0.6 + (100 - abs(c.avg_bid_variance)) * 0.2 + c.capacity_available * 0.2
elif project.priority == 'cost':
score = (100 - c.avg_bid_variance) * 0.5 + c.performance_score * 0.3 + c.capacity_available * 0.2
elif project.priority == 'safety':
score = c.safety_score * 0.6 + c.performance_score * 0.3 + c.capacity_available * 0.1
else: # speed
score = c.capacity_available * 0.5 + c.performance_score * 0.3 + c.safety_score * 0.2
scores.append({
'contractor': c,
'score': score,
'work_match': work_match / len(project.work_types),
'cert_match': cert_match / len(project.required_certs) if project.required_certs else 1.0
})
# Sort and return top matches
scores.sort(key=lambda x: x['score'], reverse=True)
return scores[:top_n]
# Example
contractors = [
Contractor("C001", "ABC Builders", ["concrete", "structural"], ["ISO9001", "OHSAS18001"],
85, 90, ["Moscow", "SPB"], 60, -5),
Contractor("C002", "XYZ Construction", ["concrete", "finishing"], ["ISO9001"],
78, 85, ["Moscow"], 80, 10),
]
project = ProjectRequirement("P001", ["concrete"], ["ISO9001"], "Moscow", 1000000, "quality")
matches = match_contractors(project, contractors)
for m in matches:
print(f"{m['contractor'].name}: Score {m['score']:.1f}")
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.
- 8d ago First seen · 742 lines · 33 tokens per session scan A a236d5d95a4e
contractor-matching-ai 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 33 tokens to every session and 5,841 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to contractor-matching-ai, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…