Results for “integrity”

Deploys canary files (honeytokens) across file systems to detect ransomware encryption activity in real time. Uses strategically placed decoy documents monitored via file integrity monitoring or OS-level watchdogs to trigger alerts when ransomware modifies or encrypts them. Activates for requests involving ransomware canary deployment, honeyfile setup, deception-based ransomware detection, or file integrity monitoring for encryption.

The English summary is being prepared. Showing the original description.

Verify supply chain integrity for AI agent plugins, tools, and dependencies. Use this skill when: - Generating SHA-256 integrity manifests for agent plugins or tool packages - Verifying that installed plugins match their published manifests - Detecting tampered, modified, or untracked files in agent tool directories - Auditing dependency pinning and version policies for agent components - Building provenance chains for agent plugin promotion (dev → staging → production) - Any request like "verify plugin integrity", "generate manifest", "check supply chain", or "sign this plugin"

The English summary is being prepared. Showing the original description.

Deploys canary files (honeytokens) across file systems to detect ransomware encryption activity in real time. Uses strategically placed decoy documents monitored via file integrity monitoring or OS-level watchdogs to trigger alerts when ransomware modifies or encrypts them. Activates for requests involving ransomware canary deployment, honeyfile setup, deception-based ransomware detection, or file integrity monitoring for encryption.

The English summary is being prepared. Showing the original description.

Detects data integrity issues including orphaned records, broken foreign key relationships, constraint violations, and provides automated fix migrations. Use for "data integrity", "orphaned records", "broken relationships", or "data quality".

The English summary is being prepared. Showing the original description.

Verify the witness chain, a linked record of evidence, for a Cognitum Seed device. Check for missing recording periods and broken hash links, report an integrity score, and save detected gaps for auditing.

• Verify a device's witness chain
• Find gaps between recording periods
• Check for broken hash links

Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.

• Checking ADR integrity after import
• Blocking CI when ADR issues are found
• Reviewing ADR data before a release

Review an existing security case package before report handoff. Check links between evidence, findings, investigation paths, tasks, and timeline entries, optionally verify file hashes to detect changes, and produce a Markdown or JSON review.

• Reviewing investigation records before report handoff
• Checking links between evidence, findings, and paths
• Verifying case artifact integrity with SHA-256

Validate generated PowerPoint decks for layout problems, accessibility, editable content, source references, and file integrity. Follow a repair and recheck workflow, keeping audit reports and build records together for delivery.

• Check generated slides before delivery
• Find overlapping content and overflowing text
• Review accessibility and editable slide objects

Investigate suspected rootkits, malware that hides its presence, by comparing process lists, inspecting memory, and checking system integrity. Use Volatility and Windows or Linux scanners to identify hidden processes, suspicious drivers, altered system calls, and concealed connections.

• Investigating compromise when standard tools show no anomalies
• Comparing process lists to find hidden activity
• Examining suspicious drivers and concealed connections

Design monitoring for industrial attacks that alter controller programs while hiding changes with false sensor readings. Compare PLC program blocks against known-good copies and check physical measurements against process models to identify suspicious inconsistencies.

• Monitoring industrial controller programs for unauthorized changes
• Investigating discrepancies between sensor readings and equipment behavior
• Planning detection across IT and industrial control systems

Audit Secure Boot settings, revoked boot components, and EFI startup files on Linux and Windows. The skill helps identify missing protections and signs of bootkits, malicious software that runs before the operating system.

• Auditing Secure Boot after a bootkit advisory
• Checking revocation updates across managed devices
• Investigating suspected bootkit infections

Check training data and machine learning models for malicious changes, including backdoors that cause unexpected behavior on specific inputs. Combine data quality checks, model analysis, and file integrity verification, then document findings and retest after remediation.

• Screening third-party data before training
• Checking downloaded model weights before deployment
• Investigating unexpected behavior on specific inputs

Check industrial process data servers for unauthorized clients and suspicious data patterns using a Python detector. Provides alerts for missing or constant values and investigation checks for attackers moving between IT and operational technology networks.

• Checking industrial historian servers for unauthorized clients
• Investigating missing or suspiciously constant process data
• Reviewing signs of movement between IT and OT networks

Collect evidence from a compromised computer before shutdown or remediation erases it. Preserve memory, network connections, processes, and system state, then record integrity hashes and handling history to support incident investigation and evidence tracking.

• Preserving evidence before shutting down a compromised computer
• Collecting memory evidence for suspected fileless malware
• Recording active connections and processes during an intrusion

Create disk images for investigations using dd or dcfldd on Linux. The workflow covers write protection, bit-for-bit copying, hash checks to verify integrity, and documentation of the acquisition process.

• Preserving a suspect drive before investigation
• Creating evidence copies of USB devices or memory cards
• Verifying that a disk image matches its source

Investigate malware hidden in boot records, UEFI firmware, or the operating system’s core. The skill guides evidence collection, boot integrity checks, firmware and memory analysis, and reporting of persistence mechanisms and remediation steps when compromise survives an OS reinstall.

• Investigating infections that survive an OS reinstall
• Examining unexplained Secure Boot integrity violations
• Finding hidden processes and suspicious kernel drivers

Find CAD models of off-the-shelf parts on step.parts using model names, standards, aliases, and dimensions. Compare matching records, download STEP files when needed, and check file integrity against a supplied checksum.

• Find a servo or motor by model number and aliases
• Compare screws and bearings by standard and dimensions
• Download a selected STEP file and check its integrity

Check experimental results before making research claims. A fresh reviewer examines reference data, score calculations, result files, and evaluation scope, then produces an evidence-based report showing which claims are supported and which need qualification.

• Checking results before writing a paper
• Verifying reference data and score calculations
• Matching reported numbers to result files

Audit research experiments before using their results to support claims. An independent model checks reference data, metric calculations, result files, and evaluation scope, producing reports with evidence, findings, and specific actions to address concerns.

• Verify the source of reference data
• Check score normalization and metric calculations
• Match paper claims against saved results

Audit npm dependencies before updating them with Bun. Check maintainers, release age, signatures, published file changes, and release notes, then update packages that pass review and record deferred updates for later follow-up.

• Auditing dependency updates before installation
• Checking maintainer changes and suspicious package contents
• Updating packages that pass integrity checks

Inspect DWARF, the debug information stored with compiled code, to find functions and types, check structural integrity, and clarify specification details. Also helps write parsing tools using libraries such as pyelftools, libdwarf, or gimli.

• Finding functions and types in debug information
• Checking DWARF structural integrity
• Comparing debug-information quality metrics

Run a submission-readiness preflight on a manuscript before arXiv upload. Use when the user is preparing an arXiv submission, asks to check a paper before uploading, mentions hallucinated or fake references, leftover LLM meta-comments / prompts in text, placeholder data (TODO, TBD, XX%), AI-use disclosure, scholarly integrity, research integrity, or arXiv moderation risk — even if they don't say "preflight". Also trigger on phrases like "check my paper before arXiv", "verify my references", "scan for AI artifacts", "scan for LLM residue", "is my submission ready", or "review .tex/.bib before submit".

The English summary is being prepared. Showing the original description.

Use whenever you run statistical analysis for the social sciences (regression, hypothesis tests, econometrics) or read Stata (.dta) / SPSS (.sav) data in this workspace. Enforces an execute-don't-interpret boundary (surface estimates, don't volunteer causal claims), checks the analysis against a preregistration plan for HARKing, verifies reproducible seeds, and reproduces .dta/.sav estimates via R. Flags integrity risks; never certifies the analysis is sound.

The English summary is being prepared. Showing the original description.

Verify device legitimacy and app integrity using DeviceCheck (DCDevice per-device bits) and App Attest (DCAppAttestService key generation, attestation, and assertion flows). Use when implementing fraud prevention, detecting compromised devices, validating app authenticity with Apple's servers, protecting sensitive API endpoints with attested requests, or adding device verification to a backend architecture.

The English summary is being prepared. Showing the original description.