disclaimer-language
Skill1.6k starsChanged 9 days agoMITView on GitHub
Verbatim CAUTION disclaimers for HVE planning, coaching, and review agents, one section per planner or review family, plus the session-state fields that track display. Preloaded by the agents that show them.
Trending
More talk lately.about the whole repository
Who's talking about microsoft/hve-core
- A Hacker News story“Microsoft/Hve-Core”Hacker News · Mar 8, 2026 · 3 points
- github/codeql“Actions: `uses: $/…` self-repository references are not resolved to local reusable workflows or composite …”GitHub · Oct 5, 2026 · 1 reactions
- @github-trending.bsky.social“📦 microsoft / hve-core ⭐ 169 (+6) 🗒 PowerShell A refined collection of Hypervelocity Engineering …”Bluesky · Mar 5, 2026 · 1 likes
- A Hacker News story“A refined collection of Hypervelocity Engineering components”Hacker News · Feb 20, 2026 · 1 points
- microsoft/vscode“hooks cannot find scripts in WSL because PLUGIN_ROOT is expanded in the wrong format (mixed / and \)”GitHub · Oct 17, 2026
The biggest 5 of 25 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 25
Talked about on GitHub, Hacker News and Bluesky (25 times).
On GitHub · 22
- Oct 5, 2026Actions: `uses: $/…` self-repository references are not resolved to local reusable workflows or composite actions (false positives and downgraded severity) — github/codeql1 reaction · 1 comment
- Oct 17, 2026hooks cannot find scripts in WSL because PLUGIN_ROOT is expanded in the wrong format (mixed / and \) — microsoft/vscode0 reactions · 1 comment
- Oct 16, 2026[Candidate] microsoft/hve-core - large collection (87 SKILL.md files) — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 12, 2026security: hve-core freshness needs attention (2 drifted, 0 check errors) — microsoft/physical-ai-toolchain0 reactions · 3 comments
- Oct 3, 2026agent-skills.github.microsoft.hve-core: init at 3.3.101 — sudosubin/agents.nix0 reactions
17 more on GitHub
- Sep 26, 2026strict-review 보강 — nayounsang/younsang-codex-plugin0 reactions
- Jul 22, 2026chore: add Copilot cloud-sandbox and dev container with hve-core-all — JoshLuedeman/fabric-worldcup0 reactions
- Jul 22, 2026chore: Copilot cloud-sandbox setup + dev container with hve-core-all — JoshLuedeman/vCamService0 reactions
- Jul 22, 2026chore: add Copilot cloud-sandbox setup + dev container (hve-core-all plugin) — JoshLuedeman/cosmosdb-to-sql-migration-tool0 reactions
- Jul 22, 2026chore: add Copilot cloud-sandbox setup + dev container with hve-core-all plugin — JoshLuedeman/my-scripts0 reactions
- Jul 20, 2026security: hve-core freshness needs attention (6 drifted, 0 check errors) — microsoft/physical-ai-toolchain0 reactions · 10 comments
- May 4, 2026feat(agents): thin GHCP cloud-agent wrapper exposing hve-core RPI — microsoft/physical-ai-toolchain0 reactions
- Apr 14, 2026Spec driven development — devndive/links0 reactions
- Apr 11, 2026Chore releases — googleapis/release-please0 reactions
- Mar 29, 2026Test: performance issues with many custom agents registered — microsoft/vscode0 reactions · 2 comments
- Mar 25, 2026Support git symlinks in plugin install on Windows — github/copilot-cli0 reactions · 3 comments
- Mar 21, 2026chore(submodules): bump external/microsoft-hve-core from `e49a1b5` to `0fbd111` — Anselmoo/copilot-plugin-manager0 reactions · 3 comments
- Mar 9, 2026feat(ai-rules): added Copilot generation, external agent fetch, and AI workflows cookbook — rios0rios0/guide0 reactions
- Feb 28, 2026mar 2026 — kimtth/azure-openai-llm-notes0 reactions
- Feb 12, 2026docs(community): document GitHub Discussions usage and create welcome post — microsoft/edge-ai0 reactions
- Feb 12, 2026fix(docs): replace Azure DevOps references in CONTRIBUTING.md with GitHub equivalents — microsoft/edge-ai0 reactions
- Feb 6, 2026chore: migrate CODEOWNERS to team-based fallback pattern — microsoft/edge-ai0 reactions
On Hacker News · 2
- Mar 8, 2026Microsoft/Hve-Core3 points
- Feb 20, 2026A refined collection of Hypervelocity Engineering components1 point
On Bluesky · 1
- Mar 5, 2026📦 microsoft / hve-core ⭐ 169 (+6) 🗒 PowerShell A refined collection of Hypervelocity Engineering components (instructions, prompts,… — @github-trending.bsky.social1 likes and repost
In this repository94 other files it gives its agents.
- .github/skills/hve-core/vally-tests/references/agents.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- accessibility-coverage-matrixSkill
- accessibilitySkill
- code-reviewSkill
- hve-artifact-authoringSkill
- python-foundationalSkill
- analysis-authoringSkill
- data-catalogSkill
- dataopsSkill
- data-science-engineering-foundationSkill
- evaluation-designSkill
- feasibilitySkill
- ml-experimentationSkill
- synth-data-generateSkill
- demo-setupSkill
- dt-coaching-foundationSkill
- dt-curriculumSkill
- dt-figma-exportSkill
- dt-methodsSkill
- dt-rpi-integrationSkill
- ux-artifactsSkill
- ux-coachingSkill
- engagement-report-conventionsSkill
- engagement-report-council-critiqueSkill
- engagement-reportingSkill
- cavemanSkill
- copilot-otel-metricsSkill
- cspell-configSkill
- customer-card-renderSkill
- demo-videoSkill
- hve-demo-materialSkill
- hve-slidesSkill
- muralSkill
- tts-voiceoverSkill
- video-to-gifSkill
- vscode-playwrightSkill
- architecture-diagramsSkill
- c4-architectureSkill
- documentationSkill
- git-commitSkill
- git-mergeSkill
- git-setupSkill
- hve-builderSkill
- pull-requestSkill
- vally-testsSkill
- hve-core-installerSkill
- adr-authorSkill
- architecture-reviewSkill
- backlog-executeSkill
- backlog-managementSkill
- backlog-planSkill
- experiment-designSkill
- functional-plannerSkill
- gitlabSkill
- jiraSkill
- outcome-hypothesisSkill
- performance-slo-plannerSkill
- privacy-by-designSkill
- privacy-standardsSkill
- The first 60 shown.
The file
Files
Disclaimer Language
Planning and review agents display a CAUTION disclaimer at startup or when presenting findings. Each H2 section below is the verbatim disclaimer for one planner or review family and is loaded by its consuming artifact before use.
<!--
Authoring contract (parsed by scripts/linting/Validate-PlannerArtifacts.ps1):
- Each planner or review family gets exactly one H2 section. The first whitespace-delimited word of the heading, lowercased, is the slug (e.g. "SSSC Planning" -> "sssc"; "Code-Review" -> "code-review").
- A section may override the derived slug with exactly one `<!-- disclaimer-id: lower-kebab -->` marker immediately before its CAUTION block. The identifier must use lowercase letters or digits separated by single hyphens. Explicit metadata takes precedence; first-word derivation applies only when metadata is absent. Empty, malformed, misplaced, or repeated markers are invalid.- The slug derives: planner key
{slug}-planner; disclaimer id{slug}-full-disclaimer; disclaimer label{heading} Disclaimer. - Each H2 must contain exactly one
> [!CAUTION]blockquote; only the first is extracted. - The CAUTION prose should begin with
**Disclaimer:**(trailing colon optional); the prefix is stripped before matching against artifact footers. - Multi-line blockquote prose is joined with single spaces. -->
RAI Planning
[!CAUTION] Disclaimer: This agent is an assistive tool only. It does not provide legal, regulatory, or compliance advice and does not replace Responsible AI review boards, ethics committees, legal counsel, compliance teams, or other qualified human reviewers. The output consists of suggested actions and considerations to support a user's own internal review and decision‑making. All RAI assessments, risk classification screenings, security models, and mitigation recommendations generated by this tool must be independently reviewed and validated by appropriate legal and compliance reviewers before use. Outputs from this tool do not constitute legal approval, compliance certification, or regulatory sign‑off.
Security Planning
[!CAUTION] Disclaimer: This agent is an assistive tool only. It does not provide legal, regulatory, or compliance advice and does not replace professional security review boards, penetration testing teams, compliance auditors, legal counsel, or other qualified human reviewers. The output consists of suggested actions and considerations to support a user's own internal security review and decision‑making. All security plans, threat models, security models, and mitigation recommendations generated by this tool must be independently reviewed and validated by appropriate security and compliance reviewers before use. Outputs from this tool do not constitute security approval, compliance certification, or regulatory sign‑off.
Privacy Planning
[!CAUTION] Disclaimer: This agent is an assistive tool only. It does not provide legal, regulatory, or privacy compliance advice and does not replace privacy counsel, data protection officers, compliance teams, or other qualified human reviewers. The output consists of suggested analyses, control recommendations, and privacy considerations to support a user's own internal privacy review and decision‑making. All privacy plans, DPIA assessments, data-flow analyses, and mitigation recommendations generated by this tool must be independently reviewed and validated by appropriate privacy and compliance reviewers before use. Outputs from this tool do not constitute legal approval, privacy certification, or regulatory sign‑off.
Privacy Review
[!CAUTION] Disclaimer: This agent is an assistive review tool only. It does not provide legal, regulatory, or privacy compliance sign-off and does not replace privacy counsel, data protection officers, compliance teams, or other qualified human reviewers. The output consists of AI-assisted findings, observations, and suggested next steps to support a reviewer's own privacy analysis and decision‑making. All privacy-review findings, DPIA observations, control recommendations, and risk assessments generated by this tool must be independently reviewed and validated by a qualified privacy reviewer before acting on them or treating any finding as resolved. Outputs from this tool do not constitute legal approval, privacy certification, or regulatory sign‑off.
SSSC Planning
[!CAUTION] Disclaimer: This agent is an assistive tool only. It does not provide legal, regulatory, or compliance advice and does not replace professional supply chain security review boards, OpenSSF Scorecard evaluators, SLSA auditors, legal counsel, or other qualified human reviewers. The output consists of suggested actions, review findings, and considerations to support a user's own internal supply chain security review and decision‑making. All supply chain assessments, review reports, gap analyses, backlog items, and mitigation recommendations generated by this tool must be independently reviewed and validated by appropriate security and compliance reviewers before use. Outputs from this tool do not constitute security approval, compliance certification, or regulatory sign‑off.
Outcome-Hypothesis
[!CAUTION] Disclaimer: This skill is an assistive decision-support tool only. It does not provide financial or professional investment advice and does not replace affected stakeholders, measurement owners, accountable sponsors or decision owners, or other qualified human reviewers. The investability verdict is an evidence-readiness signal only: "investable" means the defined evidence gates passed, and "not investable" means required evidence is incomplete. All scorecards, outcome hypotheses, investability verdicts, targets, and measurement plans must be independently reviewed and validated by affected stakeholders, the measurement owner, and the accountable sponsor or decision owner before funding, commitment, or implementation. Outputs from this tool do not constitute investment approval, funding authorization, stakeholder commitment, or measurement sign-off.
ADR Planning
[!CAUTION] Disclaimer: This agent is an assistive tool only. It does not provide legal, regulatory, architectural, or compliance advice and does not replace architecture review boards, design authorities, technical leadership, legal counsel, or other qualified human reviewers. The output consists of suggested decisions, considered options, consequences, and lineage metadata to support a user's own architecture decision-making. All Architecture Decision Records, supersession lineage, ASR trigger evaluations, and handoff work items generated by this tool must be independently reviewed and validated by appropriate architecture and engineering reviewers before adoption. Outputs from this tool do not constitute architectural approval, design sign-off, or compliance certification.
PRD Requirements Planning
[!CAUTION] Disclaimer: This agent is an assistive tool only. It does not provide product management approval, technical feasibility validation, or business sign-off and does not replace product managers, engineering leads, business stakeholders, or other qualified human reviewers. The output consists of suggested requirements, acceptance criteria, and product specifications to support a user's own product planning and decision-making. All Product Requirements Documents, functional requirements, non-functional requirements, and constraint definitions generated by this tool must be independently reviewed and validated by appropriate product and engineering reviewers before adoption. Outputs from this tool do not constitute product approval, requirements sign-off, or engineering commitment.
BRD Requirements Planning
[!CAUTION] Disclaimer: This agent is an assistive tool only. It does not provide business approval, regulatory compliance validation, or executive sign-off and does not replace business analysts, stakeholder representatives, compliance teams, or other qualified human reviewers. The output consists of suggested business requirements, objectives, and scope definitions to support a user's own business analysis and decision-making. All Business Requirements Documents, business objectives, stakeholder analysis, and requirement traceability generated by this tool must be independently reviewed and validated by appropriate business and compliance reviewers before adoption. Outputs from this tool do not constitute business approval, requirements sign-off, or stakeholder commitment.
Design Thinking Coaching
[!CAUTION] Disclaimer: This agent is an assistive coaching tool only. It does not conduct user research, observe stakeholders, or speak for the people whose problems you are designing for, and it does not replace primary research, direct stakeholder contact, design review, or product and strategy decision authority. Personas, problem statements, journey maps, empathy maps, concept tests, and other Design Thinking artifacts produced with this tool are scaffolding for your own research and synthesis — not substitutes for real stakeholder voice or observed behavior. Validate all AI-generated assumptions, personas, themes, and insights against actual stakeholders before treating any Design Thinking artifact as a basis for product, design, or strategy commitments. Outputs from this tool do not constitute validated research findings or design approval.
Data Science and Engineering Coaching
<!-- disclaimer-id: data-science-engineering -->[!CAUTION] Disclaimer: This agent is an assistive data-science and data-engineering coaching tool only. It does not validate customer data, execute production pipelines, establish model fitness, or replace data owners, privacy and Responsible AI reviewers, engineering review, or business decision authority. Catalogs, feasibility findings, analyses, experiments, tests, and operational recommendations generated with this tool may be incomplete or inaccurate and must be independently reviewed against approved data sources, stakeholder evidence, and organizational controls before use. Outputs from this tool do not constitute data approval, feasibility sign-off, model approval, privacy or Responsible AI approval, or production readiness.
Code-Review
[!CAUTION] Disclaimer: This agent is an assistive review tool only. It does not provide engineering sign-off, security certification, or compliance approval and does not replace qualified human code review, security review boards, or other professional reviewers. The output consists of AI-assisted findings, observations, and suggested remediations to support a reviewer's own analysis and decision-making. All code-review findings — including functional, standards, and accessibility observations — generated by this tool must be independently reviewed and validated by a qualified human reviewer before acting on them, merging changes, or treating any finding as resolved. Outputs from this tool do not constitute engineering approval, merge authorization, or compliance certification.
Security-Review
[!CAUTION] Disclaimer: This agent is an assistive review tool only. It does not provide legal, regulatory, or compliance advice and does not replace professional security review boards, penetration testing teams, compliance auditors, or other qualified human reviewers. The output consists of AI-assisted findings, risk observations, and suggested remediations to support a reviewer's own security analysis and decision-making. All security-review findings, vulnerability assessments, and remediation recommendations generated by this tool must be independently reviewed and validated by a qualified security reviewer before acting on them or treating any finding as resolved. Outputs from this tool do not constitute security approval, compliance certification, or regulatory sign-off.
Accessibility-Review
[!CAUTION] Disclaimer: This agent is an assistive review tool only. It does not provide accessibility conformance certification or legal compliance sign-off and does not replace professional accessibility audits, assistive-technology user testing, or other qualified human reviewers. The output consists of AI-assisted findings, success-criteria observations, and suggested remediations to support a reviewer's own accessibility analysis and decision-making. All accessibility-review findings, conformance assessments, and remediation recommendations generated by this tool must be independently reviewed and validated by a qualified accessibility reviewer before acting on them or treating any finding as resolved. Outputs from this tool do not constitute accessibility conformance certification or legal compliance sign-off.
Canonical session-state fields consumed by this disclaimer protocol
Planning and coaching agents that adopt this disclaimer protocol persist acknowledgment in their session state file (state.json for planners; coaching-state.md YAML for the DT Coach). The following field is required:
disclaimerShownAt— ISO 8601 timestamp recording the most recent time the full disclaimer was shown to the user. Set tonulluntil first display, leave unchanged during normal continuation, and update only when the full disclaimer is actually shown again. This field is not the immutable first-display audit record; thenoticeLogarray preserves the display history.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

