Triage Codeql
netdata/netdata
Inspect, review or triage GitHub Code Scanning alerts, including CodeQL findings; apply verified dismissals when authorized.
How to monitor and fix security issues in Massing — CodeQL alerts, dependency audits, secret scanning, and ReDoS/XXE fixes.
$ npx skills add ibuilder/massing --skill security-monitoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ibuilder/massing security-monitoring --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ibuilder/massing.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/security-monitoring .claude/skills/security-monitoring && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "security-monitoring" agent skill from https://github.com/ibuilder/massing/tree/main/.claude/skills/security-monitoring into .claude/skills/security-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-monitoring", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ibuilder/massing/tree/main/.claude/skills/security-monitoringType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ibuilder/massing --skill security-monitoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ibuilder/massing security-monitoring --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ibuilder/massing.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/security-monitoring .agents/skills/security-monitoring && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "security-monitoring" agent skill from https://github.com/ibuilder/massing/tree/main/.claude/skills/security-monitoring into .agents/skills/security-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-monitoring", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ibuilder/massing --skill security-monitoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ibuilder/massing security-monitoring --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ibuilder/massing.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/security-monitoring .cursor/skills/security-monitoring && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "security-monitoring" agent skill from https://github.com/ibuilder/massing/tree/main/.claude/skills/security-monitoring into .cursor/skills/security-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-monitoring", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ibuilder/massing.git --path .claude/skills/security-monitoring--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ibuilder/massing --skill security-monitoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ibuilder/massing security-monitoring --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ibuilder/massing.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/security-monitoring .gemini/skills/security-monitoring && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "security-monitoring" agent skill from https://github.com/ibuilder/massing/tree/main/.claude/skills/security-monitoring into .gemini/skills/security-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-monitoring", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ibuilder/massing security-monitoringInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ibuilder/massing --skill security-monitoring -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ibuilder/massing.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/security-monitoring .github/skills/security-monitoring && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "security-monitoring" agent skill from https://github.com/ibuilder/massing/tree/main/.claude/skills/security-monitoring into .github/skills/security-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-monitoring", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ibuilder/massing --skill security-monitoring -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ibuilder/massing security-monitoring --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ibuilder/massing.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/security-monitoring .opencode/skills/security-monitoring && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "security-monitoring" agent skill from https://github.com/ibuilder/massing/tree/main/.claude/skills/security-monitoring into .opencode/skills/security-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "security-monitoring", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
security-monitoringHow to monitor and fix security issues in Massing — CodeQL alerts, dependency audits, secret scanning, and ReDoS/XXE fixes.
Security Monitoring is an agent skill from ibuilder/massing. How to monitor and fix security issues in Massing — CodeQL alerts, dependency audits, secret scanning, and ReDoS/XXE fixes. Invoke after a push (standing directive) or when doing a hardening pass. Emphasises that a green CodeQL run != zero alerts.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Security, covering Static analysis and SAST and Secrets management. The repository describes itself as: Open, self-hosted, IFC-native AEC platform: web BIM viewer + modeling, a ~100-module GC portal (RFIs, pay apps, CPM, construction accounting — double-entry GL/WIP → QuickBooks… The licence is MIT.
Read from SKILL.md and the folder at commit 523e5b3. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
ghpythonnpmgitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use gh, npm and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Security Monitoring loads about 1.7k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 669 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from ibuilder/massing at commit 523e5b3, republished under its MIT licence (© ibuilder). 669 words, ~1,748 tokens.
.claude/skills/security-monitoring/SKILL.md (or your agent's skills folder).Standing directions for this repo: docs/roadmap-directions.md. Read those first.
Standing directive: check CodeQL after every push and fix any HIGH that appears.
A "CodeQL Advanced" workflow run showing completed success only means the scan executed — it does NOT mean zero alerts. Alerts live in the code-scanning API:
gh api repos/ibuilder/massing/code-scanning/alerts --jq '[.[] | select(.state=="open")] | length'
gh api "repos/ibuilder/massing/code-scanning/alerts?state=open&per_page=30" \
--jq '.[] | "\(.rule.security_severity_level // .rule.severity) | \(.rule.id) | \(.most_recent_instance.location.path):\(.most_recent_instance.location.start_line)"'After pushing a fix, wait for the next CodeQL run to re-scan, then re-query — the count drops when alerts auto-close.
py/polynomial-redos (ReDoS): a free-text scanner using unbounded \d+ / [\d,]+ / \s* under re.search re-scans → polynomial on a crafted long string. Fix: bound the quantifiers ({1,n} not +/*) and cap the input (text[:20_000]) before the regex. Verify detection still works on real inputs + a 100k-char crafted input returns in <100 ms.defusedxml.ElementTree.fromstring (catch ET.ParseError + defusedxml.common.DefusedXmlException → return empty). Never bare xml.etree.py/weak-sensitive-data-hashing, bandit B324): SHA-1/MD5 used for non-crypto identity/cache keys → add usedforsecurity=False.cd apps/web && npm audit --omit=dev
cd services/api && ./.venv/Scripts/python.exe -m bandit -r src ../data/src -ll -ii # HIGH+MED, high-confidence
cd services/api && ./.venv/Scripts/python.exe -m pip_audit --progress-spinner off # pip install pip-audit first
# secret scan (no gitleaks): grep the source tree for high-signal patterns, exclude node_modules/venv/testsPin CVE'd transitive deps in services/data/requirements.txt (e.g. pillow>=12.3.0).
Difficulty follows structure, not severity: multi-file / cross-import data flows are the hardest class to localize and the least covered by SAST pattern matching. Prioritize hand/agentic review on flows spanning router → dependency helper → model/engine → storage (request data crossing module boundaries), not single-file sinks CodeQL already patterns. SAST is coverage-limited by its rules; the search→verify→refine agentic review (the security-review subagent + this checklist) is the complement, not a duplicate.
Run over a release range (git diff vX..vY --stat, then read the changed files). Every class below
produced a real finding in the v0.3.510 HARDEN-2 pass:
routers/jobs.py _KIND_MIN_ROLE), bulk endpoints, MCP dispatch.
New privileged operations must gate every path, not just the front door, and audit each.rule_library.MAX_* is
the pattern; schedule_baselines._MAX too).order_by(asc).limit() silently hides everything
created after row N — cap with desc().limit() then re-sort ascending for stable display.esc() (panels,
from ui/charts) or escapeHtml (viewer). Numbers/.toFixed/server-constant labels are fine.
CodeQL catches some (js/xss-through-dom) but not all sinks._find_op
fix); validate what stored selectors will DO, not just that they parse — a silently-never-matching
rule is a false "pass" downstream.onClose hook
(ui/result.ts showResult(title, render, onClose)) — closing must stop timers + restore state.<Summary>1</Summary>; XER non-TASK
tables) — named+dated summary rows import as phantom records otherwise.aec_api.supply_chain is a dependency-free (stdlib importlib.metadata) supply-chain tool:
cd services/api && PYTHONPATH="src;../data/src" ./.venv/Scripts/python.exe -m aec_api.supply_chain # informational
cd services/api && PYTHONPATH="src;../data/src" ./.venv/Scripts/python.exe -m aec_api.supply_chain --gate # exit 1 on STRONG copyleftmpl).--gate fails only on STRONG copyleft, so it never breaks CI over the known LGPL/MPL core deps. Known strong hits are venv-incidental, NOT declared deps (e.g. pymupdf/AGPL, pyinstaller/GPL build tool) — confirm a strong hit is absent from services/*/requirements* before acting; a declared strong-copyleft dep is a real violation to remove.supply_chain.sbom() emits a minimal CycloneDX 1.5 component list. supply_chain.pdf_sanity(bytes) is a lightweight pre-ingest PDF check (header/EOF/size + active-content flags: JavaScript/Launch/EmbeddedFile/OpenAction) — NOT a full parser (no AGPL PyMuPDF).Per the security-review exclusions: DoS/resource-exhaustion, secrets-on-disk (handled elsewhere), rate-limiting, SSRF that only controls the path, client-side authz, log-spoofing, outdated-dep advisories (handled separately). Fix concrete, exploitable HIGH/MED with a clear path.
See memory: codeql-monitoring, perf-sec-p0-patterns, innerhtml-xss-esc, query-dsl-selector-spine.
© ibuilder, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/security-monitoring of ibuilder/massing.
Open the folder on GitHubat commit 523e5b3
Security Monitoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Security Monitoring this skillibuilder/massing | 122 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Triage Codeqlnetdata/netdata | 81k | — | ~1.8k | Automated safety check: Notes | GPL-3.0 | |
| Sast Hardcodedsecretsutkusen/sast-skills | 1.3k | — | ~6.5k | Automated safety check: Notes | MIT | |
| Implementing GitHub Advanced Security For Code Scanningmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Aeon Vuln ScannerBankrBot/skills | 1.2k | — | ~858 | Automated safety check: Pass | None | |
| Triaging Security Findingsbitwarden/ai-plugins | 155 | — | ~2.2k | Automated safety check: Pass | Custom licence |
netdata/netdata
Inspect, review or triage GitHub Code Scanning alerts, including CodeQL findings; apply verified dismissals when authorized.
utkusen/sast-skills
Detect hardcoded sensitive data (API keys, access tokens, private keys, passwords, etc.) in publicly accessible code — frontend JavaScript, mobile apps, client-side bundles, and HTML templates.
mukul975/Anthropic-Cybersecurity-Skills
Configures GitHub Advanced Security (code scanning with CodeQL, secret scanning, dependency review, and Dependabot alerts) to perform automated static analysis and vulnerability detection across…
BankrBot/skills
Audit trending repos for real exploitable vulnerabilities and disclose responsibly — Private Vulnerability Reporting for code flaws and verified secrets, public PRs only for already-disclosed…
bitwarden/ai-plugins
This skill should be used when the user asks to "triage security findings", "fix an Aikido finding", "review Aikido issues", "dismiss a false positive", "check SAST/IaC alerts", or needs to work…
deonmenezes/mantishack
When and how to reach for the companion detectors -- bandit (Python SAST) and trivy (deps + secrets + IaC misconfig) -- alongside the core semgrep/CodeQL/osv/trufflehog toolchain
ibuilder/massing
How to run and add Python tests in the Massing API/data services.
ibuilder/massing
Drive a Massing BIM/AEC project from an AI agent over MCP — read a project's status, records, CDE, KPI and model-quality checks; run standards-compliance, schedule-risk, embodied-carbon, permit-…
ibuilder/massing
The Massing release discipline — how to ship a verified, CI-green version-numbered release direct to main.
ibuilder/massing
How to verify Massing web/viewer UI changes LIVE — full verification works; two historic "stalls" are fixed and neither was the geometry loader.
ibuilder/massing
Reason like a master builder — one mind holding an entire built-asset project from raw land through design, construction, handover, operations, and disposition, anywhere in the world.
Categories
How to monitor and fix security issues in Massing — CodeQL alerts, dependency audits, secret scanning, and ReDoS/XXE fixes. Security Monitoring is an agent skill from ibuilder/massing. How to monitor and fix security issues in Massing — CodeQL alerts, dependency audits, secret scanning, and ReDoS/XXE fixes.
Security Monitoring fits situations like: tasks that involve Static analysis and SAST; tasks that involve Secrets management.
Run `npx skills add ibuilder/massing --skill security-monitoring -a claude-code`. Or copy the skill folder (.claude/skills/security-monitoring in ibuilder/massing) into .claude/skills/security-monitoring in your project. Claude Code loads it when a task matches its description.
Run `npx skills add ibuilder/massing --skill security-monitoring -a codex`. Or copy the skill folder (.claude/skills/security-monitoring in ibuilder/massing) into .agents/skills/security-monitoring in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ibuilder/massing --skill security-monitoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/security-monitoring, .gemini/skills/security-monitoring, .github/skills/security-monitoring and .opencode/skills/security-monitoring in your project.
Going by SKILL.md and its folder, Security Monitoring needs the command-line tools its instructions call (gh, python, npm and git). Our summary lists: Python 3.
SKILL.md contains no URLs. Its commands use gh, npm and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Security Monitoring is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Security Monitoring: Triage Codeql (netdata/netdata, 81k stars), Sast Hardcodedsecrets (utkusen/sast-skills, 1.3k stars), Implementing GitHub Advanced Security For Code Scanning (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Aeon Vuln Scanner (BankrBot/skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
ibuilder (a GitHub user) maintains it in ibuilder/massing, which has 122 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 9, 2026.
Source: ibuilder/massing on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.