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 nobim-image-generatorgit 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/nobim-image-generator)<a href="https://agentmods.dev/skills/datadrivenconstruction/ddc_skills_for_ai_agents_in_construction/nobim-image-generator"><img src="https://agentmods.dev/badge/skills/datadrivenconstruction/ddc_skills_for_ai_agents_in_construction/nobim-image-generator/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/nobim-image-generator"><img src="https://agentmods.dev/badge/skills/datadrivenconstruction/ddc_skills_for_ai_agents_in_construction/nobim-image-generator.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.00032 | $0.02108 |
| Opus 5 | $0.00016 | $0.01054 |
| Sonnet 5 | $0.00006 | $0.00422 |
| Haiku 4.5 | $0.00003 | $0.00211 |
Grade A, and why
nobim-image-generator 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 13d 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:
- nobim-image-generator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
noBIM Image Generator
Business Case
Problem Statement
Creating visualizations from BIM models typically requires:
- Expensive BIM software licenses
- Manual screenshot capture
- Time-consuming rendering
- Impossible to batch process
Solution
noBIM tool extracts data and generates visualizations using Python libraries, processing hundreds of projects without BIM software.
Business Value
- No license required - Pure Python solution
- Batch processing - Generate images for 1000s of projects
- Customizable - Create exactly the visualizations you need
- Automatable - Integrate into data pipelines
Technical Implementation
Installation
pip install pandas matplotlib seaborn plotly ifcopenshell
Core Functionality
import pandas as pd
import matplotlib.pyplot as plt
from mpl_toolkits.mplot3d import Axes3D
import numpy as np
from pathlib import Path
from typing import List, Optional, Tuple
class NoBIMVisualizer:
def __init__(self):
self.elements = None
self.project_name = ""
def load_from_excel(self, xlsx_path: str) -> int:
"""Load BIM data from converted Excel file."""
self.elements = pd.read_excel(xlsx_path, sheet_name="Elements")
self.project_name = Path(xlsx_path).stem
return len(self.elements)
def generate_3d_scatter(self, output_path: str,
color_by: str = "Category",
size: Tuple[int, int] = (12, 10)) -> str:
"""Generate 3D scatter plot of elements."""
if not all(col in self.elements.columns
for col in ['BBox_CenterX', 'BBox_CenterY', 'BBox_CenterZ']):
raise ValueError("Bounding box data required. Export with 'bbox' option.")
fig = plt.figure(figsize=size)
ax = fig.add_subplot(111, projection='3d')
# Get unique categories for coloring
categories = self.elements[color_by].unique()
colors = plt.cm.tab20(np.linspace(0, 1, len(categories)))
color_map = dict(zip(categories, colors))
for cat in categories:
subset = self.elements[self.elements[color_by] == cat]
ax.scatter(
subset['BBox_CenterX'],
subset['BBox_CenterY'],
subset['BBox_CenterZ'],
c=[color_map[cat]],
label=cat[:20],
alpha=0.6,
s=10
)
ax.set_xlabel('X')
ax.set_ylabel('Y')
ax.set_zlabel('Z')
ax.set_title(f'{self.project_name} - 3D Element Distribution')
ax.legend(loc='upper left', fontsize=8, ncol=2)
plt.savefig(output_path, dpi=150, bbox_inches='tight')
plt.close()
return output_path
def generate_floor_plan(self, output_path: str, level: str,
size: Tuple[int, int] = (14, 10)) -> str:
"""Generate floor plan visualization for specific level."""
level_elements = self.elements[self.elements['Level'] == level]
if level_elements.empty:
raise ValueError(f"No elements found for level: {level}")
fig, ax = plt.subplots(figsize=size)
# Draw walls
walls = level_elements[level_elements['Category'] == 'Walls']
for _, wall in walls.iterrows():
rect = plt.Rectangle(
(wall['BBox_MinX'], wall['BBox_MinY']),
wall['BBox_MaxX'] - wall['BBox_MinX'],
wall['BBox_MaxY'] - wall['BBox_MinY'],
fill=True, facecolor='gray', edgecolor='black', alpha=0.7
)
ax.add_patch(rect)
# Draw rooms
rooms = level_elements[level_elements['Category'] == 'Rooms']
for _, room in rooms.iterrows():
center_x = (room['BBox_MinX'] + room['BBox_MaxX']) / 2
center_y = (room['BBox_MinY'] + room['BBox_MaxY']) / 2
ax.annotate(room.get('RoomName', 'Room'),
(center_x, center_y), ha='center', fontsize=8)
ax.set_aspect('equal')
ax.set_title(f'{self.project_name} - {level}')
ax.set_xlabel('X (m)')
ax.set_ylabel('Y (m)')
plt.savefig(output_path, dpi=150, bbox_inches='tight')
plt.close()
return output_path
def generate_category_chart(self, output_path: str,
size: Tuple[int, int] = (12, 8)) -> str:
"""Generate bar chart of element categories."""
cat_counts = self.elements['Category'].value_counts().head(20)
fig, ax = plt.subplots(figsize=size)
bars = ax.barh(cat_counts.index, cat_counts.values,
color=plt.cm.viridis(np.linspace(0, 1, len(cat_counts))))
ax.set_xlabel('Element Count')
ax.set_title(f'{self.project_name} - Element Categories')
# Add count labels
for bar, count in zip(bars, cat_counts.values):
ax.text(bar.get_width() + 1, bar.get_y() + bar.get_height()/2,
f'{count}', va='center', fontsize=9)
plt.tight_layout()
plt.savefig(output_path, dpi=150, bbox_inches='tight')
plt.close()
return output_path
def generate_volume_treemap(self, output_path: str) -> str:
"""Generate treemap of volumes by category."""
import plotly.express as px
vol_by_cat = self.elements.groupby('Category')['Volume'].sum().reset_index()
vol_by_cat = vol_by_cat[vol_by_cat['Volume'] > 0].sort_values('Volume', ascending=False)
fig = px.treemap(
vol_by_cat.head(30),
path=['Category'],
values='Volume',
title=f'{self.project_name} - Volume Distribution'
)
fig.write_image(output_path)
return output_path
def batch_generate(self, xlsx_files: List[str], output_dir: str) -> List[str]:
"""Generate standard visualizations for multiple projects."""
output_dir = Path(output_dir)
output_dir.mkdir(parents=True, exist_ok=True)
generated = []
for xlsx in xlsx_files:
try:
self.load_from_excel(xlsx)
base_name = Path(xlsx).stem
# Generate all visualizations
self.generate_3d_scatter(str(output_dir / f"{base_name}_3d.png"))
self.generate_category_chart(str(output_dir / f"{base_name}_categories.png"))
generated.append(base_name)
print(f"Generated visualizations for: {base_name}")
except Exception as e:
print(f"Error processing {xlsx}: {e}")
return generated
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.
- 13d ago First seen · 274 lines · 32 tokens per session scan A cbc93530fdcc
nobim-image-generator is a skill published in the GitHub repository datadrivenconstruction/DDC_Skills_for_AI_Agents_in_Construction (310 stars, last pushed 21d ago), licensed MIT. It adds 32 tokens to every session and 2,108 once invoked, about $0.0002 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-08-30.
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.
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
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.