gh-aw-threat-detection is the threat detection component for GitHub Agentic Workflows (gh-aw). It is a Go CLI (threat-detect) that analyzes artifacts produced by AI agents — prompts, agent output, git patches, comment memory — and decides whether to allow or block the downstream safe-outputs job. The component runs in two main contexts: It detects three categories: prompt injection, secret leak, and malicious patch, and emits a strict JSON contract. Run these from the repo root. They are the canonical entry points…
This repository contains a sample JavaScript application used in the AI-SIP (AI-enhanced Software development In Practice) workshop. The application visualizes file system structures as an interactive graph using D3.js, providing…
316mo agoReviewMountCreate a free account to mount
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> The…
The Operation Cache Controller is a Kubernetes operator built with kubebuilder v4 framework that manages operations and caches the outcome of those operations. It provisions resources, pre-provisions resources for future use (caching), and manages the lifecycle of resources and cache. The controller manages four main Custom Resource Definitions (CRDs) in the controller.azure.github.com API group: The project follows a handler-based reconciliation pattern with clear separation of concerns: The main reconcilers are located in internal/controller/: - RequirementReconciler - Creates Cache and Operation…
Always run them through run_tests.sh. A raw godot ... gut_cmdln.gd command skips the checks at the bottom of that script, and those catch the two ways a suite goes green…
Public docs cover the public API only: MCP spec features MobileBuildMCP implements (structured content, resources, notifications, tool annotations, and so on), tools and what they do, MCP resources, configuration, session…
Guidance for coding agents working in this repository. This is a Next.js 16 demo app for the AI Engineer World's Fair 2026 schedule. It showcases cached and dynamic data fetching,…
Housekeeper is an MCP-first application: by default it runs an HTTP MCP server (streamable HTTP transport) that gives AI assistants read-only access to ClickHouse and Prometheus/Victoria Metrics, plus an optional in-account LLM diagnosis tool. With --analyze, runs a one-shot Gemini-based error analysis (agent.go, slack.go, clickhouse.go) and posts to Slack. Legacy; not used in MCP server deployments. Priority: CLI flags > env vars > config file > defaults. Notable keys beyond connection params: The server is deployment-agnostic: everything operator-facing is set…
A Go CLI that validates and compiles markdown changefiles (.change.md) into a unified changelog. Used across Stripe SDK repos, both as a standalone CLI and as a Go dependency. Module: github.com/stripe/hark changefile/ and releases/ are the public API — other Go code imports them, so treat their names and signatures as a compatibility surface. cmd/ is not: the CLI is not meant to be embedded, and exports only Execute. The paths hark uses are hardcoded, not configurable: .hark/releases.json, .hark/changes/*.change.md, .hark/intros/intro-<version>.md,…
This project uses Ultracite, a zero-config preset that enforces strict code quality standards through automated formatting and linting. Oxlint + Oxfmt (the underlying engine) provides robust linting and formatting. Most…
This document describes the coding conventions and patterns used in this repository for implementing Azure Pipelines schemas in KCL. Don't use relative imports: For file-level documentation (especially for types): Pattern: type Name = SimpleForm | ComplexForm | ... Don't create separate schemas for identical structures:
This project follows strict C# coding standards. All code must adhere to these guidelines. Every .cs file must start with: These are error-level requirements:
110mo agoReviewMountCreate a free account to mount
This is an n8n community node package for integrating Sentry with n8n workflows. The package provides a custom node that sends structured log messages to Sentry using the official @sentry/node SDK. It follows the n8n node development standards and uses TypeScript with strict type checking. The Sentry node allows users to send structured logs from n8n workflows to Sentry. Features include: - Configurable Sentry DSN (Data Source Name) - Support for all Sentry log levels: trace, debug, info, warn, error,…
113mo agoReviewMountCreate a free account to mount
This is an Astro Starlight documentation site for the Sentry Build Academy workshop. The site teaches developers how to implement comprehensive observability with Sentry in fullstack JavaScript applications using Vite…
118mo agoReviewMountCreate a free account to mount
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.