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 datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction --skill uberization-readinessgit clone --depth 1 https://github.com/datadrivenconstruction/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/datadrivenconstruction/ddc_skills_for_ai_agents_in_construction/uberization-readiness)<a href="https://agentmods.dev/skills/datadrivenconstruction/ddc_skills_for_ai_agents_in_construction/uberization-readiness"><img src="https://agentmods.dev/badge/skills/datadrivenconstruction/ddc_skills_for_ai_agents_in_construction/uberization-readiness/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/datadrivenconstruction/ddc_skills_for_ai_agents_in_construction/uberization-readiness"><img src="https://agentmods.dev/badge/skills/datadrivenconstruction/ddc_skills_for_ai_agents_in_construction/uberization-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.02418 |
| Opus 5 | $0.00015 | $0.01209 |
| Sonnet 5 | $0.00006 | $0.00484 |
| Haiku 4.5 | $0.00003 | $0.00242 |
Grade A, and why
uberization-readiness 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- uberization-readiness — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Uberization Readiness Assessment
Overview
The construction industry faces disruption from open data platforms that bring transparency to pricing, quality, and performance. Companies that fail to adapt risk being "uberized" out of the market.
"Traditional business model often thrives on opacity... Automation and open data bring radical transparency." — Artem Boiko
"Working with construction companies on process automation is like trying to build a copy of Uber for taxi drivers at an airport in 2005." — Artem Boiko
What is Construction Uberization?
┌─────────────────────────────────────────────────────────────────┐
│ TRADITIONAL vs UBERIZED CONSTRUCTION │
├─────────────────────────────────────────────────────────────────┤
│ │
│ TRADITIONAL MODEL UBERIZED MODEL │
│ ───────────────── ────────────── │
│ │
│ • Opaque pricing • Transparent rates │
│ • Relationship-based • Performance-based │
│ • Manual processes • Automated workflows │
│ • Information asymmetry • Open data access │
│ • Proprietary data • Shared databases │
│ • Slow decision making • Real-time analytics │
│ │
│ "Knowledge is power" "Data is shared" │
│ │
└─────────────────────────────────────────────────────────────────┘
Readiness Assessment Framework
from dataclasses import dataclass
from enum import Enum
from typing import List, Dict
class ReadinessLevel(Enum):
VULNERABLE = 1 # High disruption risk
REACTIVE = 2 # Responding to change
ADAPTIVE = 3 # Actively transforming
LEADING = 4 # Driving change
@dataclass
class AssessmentDimension:
name: str
current_state: str
target_state: str
score: int # 1-10
actions: List[str]
def assess_uberization_readiness(company_data: dict) -> dict:
"""Assess company readiness for industry disruption"""
dimensions = []
# 1. Data Transparency
dimensions.append(AssessmentDimension(
name="Data Transparency",
current_state=company_data.get("pricing_model", "opaque"),
target_state="Transparent pricing with clear breakdowns",
score=rate_transparency(company_data),
actions=[
"Publish rate cards for standard work items",
"Use CWICR codes for consistent pricing",
"Provide detailed estimate breakdowns"
]
))
# 2. Process Automation
dimensions.append(AssessmentDimension(
name="Process Automation",
current_state=company_data.get("automation_level", "manual"),
target_state="Automated workflows with minimal manual intervention",
score=rate_automation(company_data),
actions=[
"Implement ETL pipelines for data processing",
"Automate daily reporting",
"Deploy AI for document processing"
]
))
# 3. Data Accessibility
dimensions.append(AssessmentDimension(
name="Data Accessibility",
current_state=company_data.get("data_access", "siloed"),
target_state="Real-time data access for all stakeholders",
score=rate_accessibility(company_data),
actions=[
"Deploy dashboards for clients",
"Provide API access to project data",
"Eliminate data silos"
]
))
# 4. Performance Metrics
dimensions.append(AssessmentDimension(
name="Performance Tracking",
current_state=company_data.get("kpi_tracking", "none"),
target_state="Real-time KPIs with historical benchmarks",
score=rate_performance(company_data),
actions=[
"Track cost variance per project",
"Measure schedule performance index",
"Monitor quality metrics"
]
))
# 5. Open Standards Adoption
dimensions.append(AssessmentDimension(
name="Open Standards",
current_state=company_data.get("standards", "proprietary"),
target_state="Full adoption of open data standards",
score=rate_standards(company_data),
actions=[
"Adopt IFC for BIM data exchange",
"Use CWICR for work item classification",
"Implement open APIs"
]
))
# Calculate overall readiness
total_score = sum(d.score for d in dimensions)
max_score = len(dimensions) * 10
readiness_pct = (total_score / max_score) * 100
if readiness_pct < 30:
level = ReadinessLevel.VULNERABLE
elif readiness_pct < 50:
level = ReadinessLevel.REACTIVE
elif readiness_pct < 75:
level = ReadinessLevel.ADAPTIVE
else:
level = ReadinessLevel.LEADING
return {
"dimensions": dimensions,
"total_score": total_score,
"max_score": max_score,
"readiness_percentage": readiness_pct,
"readiness_level": level.name,
"risk_assessment": generate_risk_assessment(level, dimensions)
}
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 · 352 lines · 29 tokens per session scan A 685f65f40075
uberization-readiness is a skill published in the GitHub repository datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction (312 stars, last pushed 21d ago), licensed MIT. It adds 29 tokens to every session and 2,418 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
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
ecto-patterns
Ecto patterns — schemas, changesets, queries, migrations, Multi, associations, preloads, upserts. Use when editing Repo calls, Ecto.Query, or schema fields. Skip for Ash.
phx-research
Research Elixir/Phoenix/Ecto topics or evaluate Hex libraries (--library). Use when learning about libraries, patterns, or comparing approaches. Searches HexDocs, ElixirForum, GitHub.
document
Generate @moduledoc/@doc for tested Elixir features; may update their README section or ADR. Not for docs lookup, documentation audits/reviews, or capturing standalone decisions.
deep-research
Deep research and discovery before building something new. Explores local projects for reusable code, researches competitors, reads forums and reviews, analyses plugin ecosystems, investigates technical options, and produces a comprehensive research brief. Three depths: focused (30 min), wide (1-2 hours), deep (3-6…